backend-code-reviewlisted

# Backend Code Review ## When to use this skill Use this skill whenever the user asks to **review, analyze, or improve** backend code (e.g., `.py`) under the `api/` directory. Supports the following review modes: - **Pending-change review**: when the user asks to review current changes (inspect staged/working-tree files slated for commit to get the changes). - **Code snippets review**: when the user pastes code snippets (e.g., a function/class/module excerpt) into the chat and asks for a review. - **File-focused review**: when the user points to specific files and asks for a review of those files (one file or a small, explicit set of files, e.g., `api/...`, `api/app.py`). Do NOT use this skill when: - The request is about frontend code or UI (e.g., `.tsx`, `.ts`, `.js`, `web/`). - The user is not asking for a review/analysis/improvement of backend code. - The scope is not under `api/` (unless the user explicitly asks to review backend-related changes outside `api/`). ## How to use this skill Follow these steps when using this skill: 1. **Identify the review mode** (pending-change vs snippet vs file-focused) based on the user’s input. Keep the scope tight: review only what the user provided or explicitly referenced. 2. Follow the rules defined in **Checklist** to perform the review. If no Checklist rule matches, apply **General Review Rules** as a fallback to perform the best-effort review. 3. Compose the final output strictly follow the **Required Output Format**. No