review

# Code Review Holistic pre-merge review of completed work against the original plan. **Announce:** "Using review to assess this work before merge." ## The Iron Law ``` NO MERGE WITHOUT CODE REVIEW ``` ## Context The plan or requirements being reviewed: $ARGUMENTS Dispatch the code-reviewer agent with this prefix so the subagent sees the navigation index (subagents do not inherit parent history): ``` @ATLAS.md (navigation index — use Module Map + Key Symbols to locate touched modules) @CLAUDE.md (conventions, rules) ``` Omit either reference if the file doesn't exist. ## Your Review 1. Get the git diff: ```bash BASE_SHA=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD develop 2>/dev/null || git merge-base HEAD master 2>/dev/null) git diff $BASE_SHA..HEAD ``` 2. Read the plan/requirements referenced above 3. Review for: - **Plan alignment** — Does implementation match what was planned? - **Code quality** — Clean, maintainable, well-tested? - **Architecture** — SOLID, good separation, integrates well? - **Security** — No vulnerabilities, input validated, secrets safe? 4. Report: - **Strengths** — What was done well - **Issues** — Critical / Important / Minor with `file:line` references - **Assessment** — Ready to merge? Yes / No / With fixes After review, offer: "Ready to ship?" → chains to `/turbocharge:ship` ## Red Flags — Rationalizations That Mean You're Doing a Shallow Review If you catch yourself thinking any o...