neo-code-reviewlisted

# Code Review Specifications Apply the Reviewer Pattern. Follow this protocol strictly to systematically, objectively, and constructively review the user's code changes. --- ## 1. Perceive Phase 1. **Identify the Input Source**: - **Scenario A: Specific files are provided** - If the user provides specific file paths or directly attaches code snippets in the conversation, use them as the primary targets for review. - **Scenario B: No files are specified but inside a Git repository** - If the user asks to "review changes", "review PR", or asks for a review without providing explicit code but the project is a Git repository, **proactively run the helper script** to fetch the changes: ```bash uv run skills/neo-code-review/scripts/git-diff-reviewer.py ``` - To review only the staging area, append the `--staged` argument. - To review a specific commit range, append the `--commit <range>` argument. - **Scenario C: No changes detected and not a Git repository** - If no code input is detected and the environment is not a Git repository, gracefully prompt the user: "No code changes detected. Please provide a specific code snippet or file path." and terminate the review. 2. **Identify Programming Languages & Frameworks**: - Identify the programming language (e.g., TypeScript, C#, Python) and relevant frameworks in the code changes to apply language-specific style standards in subsequent phases. --- ## 2. Reason Phase 1. *