requesting-code-reviewlisted

# Requesting Code Review Request review early to catch issues before they spread. ## When - After completing a plan task or batch - After major refactor/feature work - Before merge or PR finalization ## How 1. Determine review range (`BASE_SHA` -> `HEAD_SHA`). 2. Check for `context-snapshot.json` at the project root: - If present: run `git rev-parse HEAD` and compare to `git_hash` in the file. - **Hashes match (fresh):** use `changed_files` and `blast_radius` as the review scope. Inject this summary into the code-reviewer prompt: *"Changed files: [list]. Also referenced by: [blast_radius callers]."* - **Hashes differ (stale):** note the snapshot is from a previous commit; use `changed_files` as a starting point but do not rely on `blast_radius`. - If absent: determine scope from `git diff --name-only BASE_SHA..HEAD_SHA` directly. 3. Dispatch `superpowers-orchestrator:code-reviewer` using `requesting-code-review/code-reviewer.md`. 4. Provide: - What changed (from context snapshot or `git diff --no-ext-diff --no-textconv`) - Scoped file list (changed files + blast radius callers if fresh snapshot available, or broad if not) - Requirement or plan reference - SHA range - Short summary ## Security Review (Built-In) When changes touch security-relevant areas, the code review **must** include a security pass. This is not a separate step — it's part of every review where applicable. **Triggers automatically when changes touch:** - Authentication