Code Review Orchestrator FAQs

Question 1

How do I trigger the review?

Accepted Answer

After ensuring all tests pass, you announce the skill usage, identify the git SHAs for the changes, and use the Task tool to dispatch a general-purpose subagent for review.

Question 2

Can I skip the review process for small changes?

Accepted Answer

No. The skill emphasizes that size does not determine bug potential. All code changes require a review to ensure safety and maintain the audit trail.

Question 3

When is a code review mandatory using this skill?

Accepted Answer

Review is required for all code changes including features, bug fixes, refactoring, and database migrations. The only exceptions are pure documentation updates and simple dependency configuration changes.

Question 4

What happens if a review returns a 'Needs Revision' status?

Accepted Answer

You must stop immediately and fix all Critical issues. Important issues must be fixed or converted to tracked tickets before you can request a follow-up review and proceed.

Question 5

How does the subagent review process work?

Accepted Answer

The skill dispatches a subagent using the code-review skill to analyze changes across six phases: plan alignment, code quality, architecture, testing, security/performance, and documentation.

Code Review Orchestrator

Key Features

Use Cases

Code Review Orchestrator

Key Features

Use Cases