requesting-code-review

Automated code review using git commit ranges works by dispatching subagents to evaluate git diffs between base and head commit SHAs against defined project requirements. This catches architectural flaws and bugs before code integration without needing manual inspection.

Subagent-driven code review is a process where subagents perform rigorous, context-specific evaluations of your git diffs. This enforces a standardized review workflow that checks code against architecture and quality standards before merging.

Yes, you need git access to compare base and head commit SHAs for code quality assessments. The subagent requires this precise git diff context to evaluate your changes accurately without being distracted by session history.

To catch architectural flaws and plan deviations before merging code, dispatch a reviewer subagent using a structured template. The subagent evaluates your git diff against your deployment plan to verify adherence to best practices.

Yes, you can use automated code review to prevent technical debt from cascading. By enforcing a subagent-driven review process before merging or proceeding to the next development task, deviations from project requirements are caught early.