requesting-code-review

Automate pre-merge code reviews by routing changes to a dedicated subagent. The reviewer evaluates provided commit ranges and plan references to catch issues early across collaborative workflows before merging to main.

Yes, you can get code review feedback without exposing private session history. The process routes precisely crafted context to a focused subagent, preserving your own session history for continued work.

To trigger a code review after task completion, you need a prior commit range and a plan reference. Dispatching the subagent with these inputs returns structured feedback documenting strengths and issues for triage.

Run a code review subagent after each task completion, major feature delivery, or before merging to main. This ensures pre-merge quality checks catch issues early across feature branches and collaborative workflows.

Yes, the automated code review outputs structured feedback for triage and fixes. Review outputs clearly document strengths and issues to guide fixes and approvals, accelerating code quality assurance.