requesting-code-review

Automate code review requests by dispatching a dedicated subagent to analyze your git diff and provide structured feedback. This Skill triggers after completing a major feature or task batch, using git SHAs to reference exact changes and categorize remediation by severity before merge.

A subagent uses git SHAs to perform diff analysis by comparing a base SHA against a head SHA to identify exact changes. You provide these SHA references when dispatching the code-reviewer, ensuring the automated feedback is anchored to specific commits in your workflow.

The best way to categorize code review feedback is by severity levels: Critical, Important, and Minor. This ensures Critical issues are fixed immediately, Important issues are resolved before proceeding, and Minor issues are documented and deferred, streamlining the remediation process before merging.

Trigger an automated code review in your git workflow after completing a task batch or major feature, or whenever a change requires independent verification. This timing ensures the subagent reviews complete, cohesive diffs via git SHAs before you attempt to merge the code.

Yes, you need to provide a template when requesting an automated code review to collect structured, consistent feedback. The template requires details like what was implemented, the plan or requirements, base and head git SHAs, and a description to guide the subagent's diff analysis.

If the code reviewer subagent flags a Critical issue, you must fix it immediately before merging. If you disagree with the reviewer's feedback on any severity level, you should provide a technical justification and evidence to override the suggested remediation.