requesting-code-reviewlisted

# Requesting Code Review Dispatch the `code-reviewer` subagent to catch issues before they accumulate. The reviewer receives only the context prepared for evaluation. It never receives the session history. This keeps the reviewer focused on the work output rather than on your thought process, and preserves your own context for follow-up work. ○ Core principle: review early, review often ## Contents - [When to Request a Review](#when-to-request-a-review) - [How to Request](#how-to-request) - [Example](#example) - [Workflow Integration](#workflow-integration) - [Red Flags](#red-flags) ## When to Request a Review □ Required - After each task in subagent-driven-development - After completing major functionality - Before merging to main □ Optional but valuable - When stuck (a fresh perspective) - Before refactoring (a baseline check) - After fixing a complex bug ## How to Request □ 1. Capture the git commit hashes ```bash BASE_SHA=$(git rev-parse HEAD~1) # or origin/main HEAD_SHA=$(git rev-parse HEAD) ``` □ 2. Dispatch the code-reviewer subagent Use the `Task` tool with the `code-reviewer` type. Fill in the `references/code-reviewer.md` template. Placeholders - `{WHAT_WAS_IMPLEMENTED}`: what you just built. - `{PLAN_OR_REQUIREMENTS}`: what you were supposed to do. - `{BASE_SHA}`: the starting commit. - `{HEAD_SHA}`: the ending commit. - `{DESCRIPTION}`: a short summary. □ 3. Respond to the feedback - Critical issues: fix immediately - Important issues: fix befor