reviewlisted

Think carefully for code review. Follow CLAUDE.md rules. ## Critical Instruction **YOU MUST use the Task tool with subagent_type to launch agents. NEVER read or analyze code files directly yourself.** Agents do the heavy lifting - you orchestrate and aggregate their results. ## Tool Strategy Use Task tool with these subagent_type values: - `explore-docs` - Documentation lookup - `explore-codebase` - Code pattern search - `explore-db` - Database schema exploration - `backend-code-optimizer` - Go code quality analysis (returns score + issues) - `frontend-code-reviewer` - React/TS code quality analysis (returns score + issues) --- ## 1. DETERMINE SOURCE & SCOPE ### Spec Handling - **Spec alone** (`/review spec:file.md`): Extract file list FROM the spec (exclusive source) - **Spec + other source** (`/review spec:file.md mode:local`): Spec provides CONTEXT, other source determines files ### File Source Priority (use first available): 1. `$ARGUMENTS.feature` -> Search codebase for feature-related files 2. `$ARGUMENTS.commit` -> `git show --name-only $ARGUMENTS.commit` 3. `$ARGUMENTS.mode` -> Git diff (pushed or local) 4. `$ARGUMENTS.spec` alone -> Extract files from spec 5. **Default**: `mode=local` (uncommitted changes) ### If mode = "pushed" (or default when no args and clean working tree) ```bash git log origin/$(git rev-parse --abbrev-ref HEAD) -1 --format="%H %s" git show --name-only --format="" HEAD git show HEAD ``` ### If mode = "local" (default) ```bash git d