requesting-code-review

To get an isolated code review before merge, you schedule a sub-agent to evaluate completed work without inheriting your session history. The reviewer assesses code quality, architecture, test coverage, and production readiness based only on the provided artifact.

A sub-agent reviews git diffs by comparing the BASE_SHA and HEAD_SHA you supply to surface precise changes. It operates in a focused evaluation context that preserves your ongoing workflow while generating structured feedback with clear severity levels.

Yes, you can run a code review without polluting your session history by scheduling a specialized sub-agent. The sub-agent operates in a focused evaluation context that does not inherit your ongoing session, ensuring it assesses only the produced artifact.

The best way to check code quality and test coverage for a completed task is using a dedicated code-review sub-agent. It evaluates your work against the plan using a templated review to provide structured feedback with clear severity and actionable fixes.

Yes, you need to provide specific git commit SHAs to trigger a focused code review. The sub-agent requires a BASE_SHA and HEAD_SHA to compare, surface precise diffs, and evaluate the exact changes before they diffuse into the main branch.