Requesting Code Review FAQs

Question 1

What does the Requesting Code Review skill do?

Accepted Answer

This skill automates the dispatch of a specialized 'code-reviewer' subagent to analyze your changes against specific project requirements and Git SHAs before you merge your work.

Question 2

When should I use this skill in my workflow?

Accepted Answer

You should use it after completing major features, after every task in subagent-driven development, and always before merging to your main branch to ensure high code quality.

Question 3

How does it integrate with Git?

Accepted Answer

The skill uses Git SHAs (BASE and HEAD) to perform context-aware commit comparisons, allowing the subagent to pinpoint exactly what changed and identify potential regressions.

Question 4

What types of feedback does the subagent provide?

Accepted Answer

The subagent provides structured feedback categorized into Critical, Important, and Minor issues, allowing you to prioritize immediate fixes versus long-term technical debt.

Question 5

How does this improve AI-driven development?

Accepted Answer

It prevents 'error cascading' by validating work at every step. By catching bugs early in the subagent cycle, it ensures that subsequent tasks are built on a stable and verified foundation.

Requesting Code Review

Key Features

Use Cases

Requesting Code Review

Key Features

Use Cases