Code Review Gatekeeper FAQs

Question 1

When is a code review mandatory using this skill?

Accepted Answer

A code review is required for all code changes, including feature additions, bug fixes, refactoring, and database migrations, before claiming work is complete or merging code.

Question 2

Are there any exceptions to the mandatory review process?

Accepted Answer

Yes, exceptions are only allowed for pure documentation updates (*.md files), simple dependency updates in configuration files, or emergency production hotfixes.

Question 3

How does the subagent perform the code review?

Accepted Answer

The skill dispatches a subagent using a six-phase framework that evaluates plan alignment, code quality, architecture, testing coverage, security/performance, and documentation.

Question 4

What should I do if a review returns a 'Needs Revision' status?

Accepted Answer

You must stop immediately, fix all identified critical and important issues, re-run your tests, and request a follow-up review before proceeding to the next task.

Question 5

Can I skip the review for very small code changes?

Accepted Answer

No. The skill is designed on the principle that trivial changes can still cause incidents. All code changes regardless of size require a review to maintain project integrity.

Code Review Gatekeeper

Key Features

Use Cases

Code Review Gatekeeper

Key Features

Use Cases