requesting-code-review

Code review for a git pull request is performed by analyzing the diff between a base SHA and head SHA. This provides categorized issues with file:line references and a merge readiness assessment to catch bugs early.

Use a code review checklist after finishing tasks, completing major features, or before merging to main. It evaluates recent code changes to detect bugs, architecture issues, and test gaps for safer merges.

Reviewing code changes between git commits requires providing the BASE_SHA, HEAD_SHA, a description of what was implemented, and a plan reference. The system inspects this diff range to produce focused feedback with file:line references.

Code review findings for production readiness are categorized into Critical, Important, and Minor issues. The output lists specific fixes, acknowledges strengths, and gives a clear verdict for merging to main.

Using a dedicated code-reviewer subagent keeps code review feedback objective. It receives only the necessary context to avoid leaking session history, ensuring an independent evaluation of your code changes.

The code review process works when stuck by dispatching a reviewer with only the necessary context to provide an independent evaluation of recent changes. This helps detect bugs and architecture issues when you need an external perspective.