Roasted Code Review FAQs

Question 1

Does this skill modify my code automatically?

Accepted Answer

No, it provides critical, actionable feedback and technical analysis. It highlights design flaws without making silent changes to your source files.

Question 2

Why does it flag more than three levels of indentation?

Accepted Answer

Following the 'Good Taste' principle, excessive nesting usually indicates a design flaw or a function doing too many things; it signals that the logic needs a redesign rather than more conditions.

Question 3

How does the 'Evidence' requirement work?

Accepted Answer

It treats missing or weak evidence in PR descriptions as a blocking issue, requiring concrete proof like terminal outputs or screenshots to ensure the change actually works in production.

Question 4

Is this skill too harsh for all projects?

Accepted Answer

It is intentionally direct and critical. It is best suited for developers and teams who want high-rigor feedback to maintain robust, scalable, and simple systems.

Question 5

What makes this review different from standard AI reviews?

Accepted Answer

It ignores stylistic nits and formatting—which linters handle—and focuses exclusively on core engineering principles, data structures, and fundamental design 'taste'.

Roasted Code Review

Key Features

Use Cases

Roasted Code Review

Key Features

Use Cases