requesting-code-review

Automating code review for a feature branch involves dispatching a specialized subagent to evaluate code changes against defined requirements and architectural standards. This skill triggers that reviewer subagent automatically based on specific git ranges to ensure production readiness before merging.

A subagent validates code changes by applying a structured prompt template to evaluate the git history range against your original plan details. This mechanism checks for plan alignment, code quality, and architectural standards to prevent drift and ensure the implementation meets requirements.

The best way to structure feedback from an automated code review is by categorizing issues into Critical, Important, and Minor tiers. This structured feedback ensures developers focus on high-impact architectural and functional issues first before addressing minor code quality suggestions.

Yes, you need git history access to run this automated code review. The reviewer subagent requires access to your git history to define the evaluation range, allowing it to accurately assess the specific code changes introduced in your feature branch or merge request.

Yes, you can use this code review automation for bug fixes and merge requests. The skill applies to software development workflows requiring systematic verification, ensuring that both new features and bug fixes are rigorously validated against architectural standards before integration.