requesting-code-review

Get the base and head commit SHAs with git rev-parse, then dispatch a code-reviewer subagent using the provided template. Fill in what was implemented, the requirements, the SHA range, and a short description.

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also useful when stuck or before refactoring to establish a baseline.

Issues are grouped into Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, optimizations). Each issue includes a file:line reference, impact, and suggested fix.

Push back with technical reasoning rather than ignoring the feedback. Show code or tests that prove the implementation works, and request clarification if the reviewer's concern is unclear.

No. The Skill explicitly flags skipping review because a change seems simple as a red flag. Critical issues must be fixed immediately and Important issues before proceeding, regardless of perceived simplicity.