claude-reviewlisted

# Claude review ## Guards - If both `git diff --staged` and `git diff main` are empty, stop: `✅ No changes to review.` ## Step 1: read context Read these in parallel from the project root, skipping any that do not exist: - `CLAUDE.md`: project type, conventions, and commands - `.claude/REQUIREMENTS.md`: feature scope and non-goals - `.claude/ARCHITECTURE.md`: technical design decisions Coding standards from `.claude/rules/` are auto-loaded by Claude Code. Always-on rules apply every session. Path-scoped rules apply to files matching their `paths:` glob. ## Step 2: get the diff and changed files Run these in parallel from the project root: ```bash git diff --staged ``` ```bash git diff --staged --name-only ``` ```bash git diff main ``` ```bash git diff main --name-only ``` If `git diff --staged` is non-empty, use it as the diff scope and use the `--staged --name-only` list as the file list. Otherwise use `git diff main` and the `main --name-only` list. ## Step 3: read changed files Read each file from the changed file list. Skip deleted files. Run reads in parallel. ## Step 4: review and persist Review the full diff and changed file contents for: 1. Bugs and edge cases 2. Error handling gaps 3. Logic flaws that will cause problems when the code is extended 4. Security issues relevant to the project context 5. Violations of rules from `.claude/rules/` that apply to the changed files Use `CLAUDE.md`, `.claude/REQUIREMENTS.md`, `.claude/ARCHITECTURE.md`, and th