requesting-code-review

A code-review subagent streamlines pull request reviews by automatically evaluating code quality, architecture, testing, and production readiness. It dispatches a dedicated reviewer subagent to generate structured feedback for each task submission without leaking session history.

Subagent-driven code review evaluates code quality, architecture, testing, and production readiness. A dispatched code-reviewer subagent generates structured feedback for each task submission, ensuring consistent evaluation without leaking session history.

Yes, you can use this code review automation for task-based development workflows. It integrates by dispatching a code-reviewer subagent for post-task reviews and pre-merge checks, applying structured evaluation to code quality, architecture, testing, and production readiness.

The best way to catch code quality issues early is to request a code review after completing a task. Dispatching a code-reviewer subagent applies automated reviewer routing to generate structured feedback on architecture, testing, and production readiness before merging.

You get structured feedback from a code review subagent by dispatching it with the required task identifiers after completing a task. The subagent generates consistent feedback evaluating code quality, architecture, testing, and production readiness without leaking session history.

Yes, automated code review routing prevents leaking session history by dispatching a dedicated code-reviewer subagent. This ensures consistent evaluation of code quality, architecture, testing, and production readiness without exposing the broader session context.