Automated Code Reviewer FAQs

Question 1

Can I skip specific findings suggested by the AI?

Accepted Answer

Absolutely. The skill stops after Phase 1 to wait for your direction. You can instruct it to fix all issues, only critical ones, or skip specific items with a reason.

Question 2

What happens if the code has many complex issues?

Accepted Answer

The skill includes a quality gate that permits up to 4 iterations. It will continue reviewing until no new findings are detected or the maximum iteration limit is reached.

Question 3

How does the two-phase review process work?

Accepted Answer

Phase 1 focuses exclusively on analysis, generating a detailed report of findings for your approval. Phase 2 only proceeds with applying fixes once you have specified which issues should be addressed.

Question 4

Can this skill run my project's existing tests?

Accepted Answer

Yes, it is designed to run backend test suites to establish a baseline before the review and to verify that applied fixes haven't introduced regressions.

Question 5

Where are the review findings stored?

Accepted Answer

Findings are documented in a standardized _code-review.md` file in your project root, which serves as a persistent record of the review history and resolution status.

Automated Code Reviewer

Key Features

Use Cases

Automated Code Reviewer

Key Features

Use Cases