requesting-code-review

To automate code review for git commits, you provide the base commit, head commit, and a task description to trigger a specialized subagent that evaluates the changes against your requirements.

A subagent-driven development workflow dispatches specialized subagents to handle specific tasks like code review, ensuring every task is validated by a dedicated agent before integration into the main branch.

You ensure code quality before merging by enforcing mandatory automated reviews after task completion, triggering a subagent to evaluate git changes and catch critical issues.

You need to provide the base commit SHA, head commit SHA, and a clear summary of the implemented work to give the reviewer context and provide targeted feedback.

Yes, automated code review verifies task requirements by evaluating git-based changes against specific task descriptions, excluding unnecessary session history to maintain focus on implementation quality.

No, the code review subagent excludes unnecessary session history to maintain focus, evaluating only the precise commit ranges and task descriptions you provide.