requesting-code-review

To get a focused code review for recent git changes, provide the base and head commit SHAs, a concise description of what was implemented, and the original plan or requirements to receive severity-classified feedback and a merge recommendation.

Reviewing code changes in subagent-driven development is best done by requesting a focused evaluation after completing each task or implementing major features to catch defects and design issues early before they compound.

Severity-classified feedback for a pull request code review works by evaluating the git range against stated requirements and categorizing all identified findings into Critical, Important, or Minor issues before delivering a clear merge assessment.

To run a code review checklist on your recent commits, you need to provide the git base SHA, head SHA, a concise description of what was implemented, and the plan or requirements to compare the changes against.

Yes, you can compare your code changes against the original plan or requirements to identify critical issues by requesting a focused evaluation that systematically classifies defects by severity and delivers a final merge recommendation.

You should request a code review to catch critical and important issues when completing tasks, implementing major features, during subagent-driven development workflows, or before merging to main to prevent regressions and reduce compounded errors.