requesting-code-review

Automated code review before a merge dispatches a dedicated code-reviewer subagent to evaluate changes, ensuring pre-merge validation and consistent feedback. It captures implemented features, plan references, and formal risk assessments.

Structured peer review in task-driven development is a formal feedback cycle where a code-reviewer subagent evaluates task completion before integration. It provides traceability by capturing what was implemented and the required plan references.

Yes, you can use a subagent workflow for quality assurance by dispatching a code-reviewer to provide focused feedback on feature implementation. This enforces timely reviews after each task to reduce integration risk.

Consistent code review feedback across codebases is achieved by automating a standardized workflow that dispatches a code-reviewer subagent. This enforces rigorous review, clear feedback, and risk management for refactoring and feature completion.

You need an automated code review subagent when rigorous review is required before integrating major features or after completing task-driven development. It ensures complete context, traceability, and a formal feedback cycle to reduce risk.

Yes, automated pre-merge validation works without external dependencies by dispatching a built-in code-reviewer subagent to evaluate changes. It applies standardized review workflows across codebases requiring rigorous quality assurance.