requesting-code-review

Automated code review dispatches a subagent to analyze changes and catch critical issues before merging a feature branch. It coordinates with Git commit tracking to provide focused context tailored to the code changes, ensuring software quality early in the cycle.

Subagent-driven development for issue tracking works by dispatching a subagent to review Git commits and provide focused context. This mechanism isolates the actual code changes from the developer's thought process to catch critical issues efficiently.

Yes, Git integration tracks commit history to facilitate the code review process. By analyzing commit changes, the review subagent receives customized context focused strictly on the code modifications, ensuring critical issues are caught early.

The best way to provide customized context for code review is using a subagent that extracts context directly from Git commit changes. This ensures reviewers evaluate the actual code modifications rather than the developer's underlying thought process.

Automated code review requires no additional dependencies to function. It operates standalone using scripts to coordinate Git integration and subagent dispatching, ensuring critical issues are caught without needing external software quality tools.

You should not use an automated code review subagent when you need a human reviewer's architectural insight or when evaluating a developer's thought process. The subagent strictly reviews focused code changes from Git commits to catch early critical issues.