neo-code-reviewlisted

# Code Review Follow this read-only workflow. Report only actionable findings supported by evidence. ## Trigger On - The user requests a code, PR, diff, commit, security, performance, test, or maintainability review. - The user asks whether code or logic is duplicated across files, or whether hard-coded values should be centralized. - An AI Agent finishes modifying code, tests, configuration, or scripts before handoff. ## Workflow 1. **Define the review scope** - Use the files or snippets supplied by the user as the primary scope. - If the user provides no scope and the current directory is a Git repository, run: ```bash uv run skills/neo-code-review/scripts/git-diff-reviewer.py --working-tree ``` - Use `--staged` for staged-only changes and `--commit <range>` for a commit range. - Read surrounding code, related tests, and existing contracts. If no reviewable input exists, report it and stop. - For a working-tree review, include the helper's tracked diff and each non-ignored untracked file as separate inputs. 2. **Load the review rules** - Read [review-checklist.md](references/review-checklist.md) before evaluating code. - Identify the actual language, framework, and affected behavior from the change. Do not infer unverified rules from filenames. 3. **Run the cross-file consistency scan** - Build the comparison set from the review targets and relevant repository source and configuration files. Use `rg --files` and the repository's