requesting-code-review

To automate code review before merging, you can coordinate a structured review process using a dedicated reviewer subagent. This requires providing git change context and a review template to evaluate requirements alignment, architecture, and production readiness.

Validating subagent-driven development for production readiness involves dispatching the completed work to an independent reviewer subagent. The reviewer evaluates code quality, testing coverage, and security against a defined review template before merge validation.

A structured code review framework handles complex debugging scenarios by applying an independent evaluation of git changes. It assesses architecture decisions and code quality to ensure the debugging solution aligns with requirements before merging.

Yes, you can use this code review process to check requirements alignment and testing coverage. The quality evaluation framework defines specific checks for these areas, alongside security and architecture decisions, to ensure production readiness.

To start a merge validation review for your git changes, you need to provide the relevant git change context and a review template. This allows the reviewer subagent to assess your feature implementation against its requirements.

A limitation of using a subagent for software development quality assurance is that it requires a predefined review template and structured git change context to function. Without this input, the subagent cannot evaluate architecture decisions or production readiness.