requesting-code-review

Automate code review by dispatching a dedicated subagent to evaluate changes for production readiness. It assesses quality, architecture, testing, and readiness using a standardized template, surfacing critical issues before merging to main.

Trigger a code review after completing each task, finishing major features, or before merging to main. It is also useful to invoke the review workflow when you are stuck or before starting a refactoring effort.

Yes, you can dispatch a code-review subagent that enforces a structured workflow with a standardized template. It generates a categorized report assessing code quality, architecture, testing, and overall readiness.

Review a specific git diff range by providing explicit base and head git references to the code-review subagent. The subagent evaluates the targeted changes and returns a categorized readiness report.

The best way to catch issues early is to route code changes to a centralized review workflow. A dedicated reviewer subagent applies structured templates to assess architecture and testing quality at task milestones.

Yes, the code review subagent operates independently without external dependencies. It relies on git diff context and standardized templates to evaluate production readiness.