Fresh-Eyes Review FAQs

Question 1

How does this skill improve my workflow?

Accepted Answer

It introduces a disciplined 4-step accountability process (Announce, Checklist, Fix, Declare). This prevents the common 'rush to ship' by forcing a 2-5 minute psychological distance to catch critical bugs like N+1 queries or race conditions.

Question 2

What specific vulnerabilities can it detect?

Accepted Answer

It focuses on high-impact issues including SQL injection, XSS, path traversal, off-by-one errors, incorrect business logic calculations, and unoptimized loops that lead to performance degradation.

Question 3

When should I use this skill?

Accepted Answer

Use this skill as the absolute last step before running a git commit, creating a Pull Request, or declaring a task finished. It is the 'last line of defense' to be executed only after all tests have passed.

Question 4

Why use this if my tests are already passing?

Accepted Answer

Passing tests only validate that the code does what you *expected* it to do. Fresh-Eyes Review is designed to find what you *didn't* expect, such as edge cases, security holes, and logic gaps that existing test suites weren't written to cover.

Question 5

What does the Fresh-Eyes Review skill do?

Accepted Answer

It serves as a mandatory final quality gate for your development process. It performs a systematic re-reading of all modified files to identify security vulnerabilities, business logic errors, and performance issues that automated tests often miss.

Fresh-Eyes Review

Fresh-Eyes Review

Key Features

Use Cases

Key Features

Use Cases