How do I install the Fresh Eyes Review skill?

Run npx skillmds@latest add majiayu000/fresh-eyes-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fresh Eyes Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fresh Eyes Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fresh Eyes Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fresh Eyes Review?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fresh Eyes Review by majiayu000 — Agent Skill

Name: Fresh Eyes Review
Rating: 4.2 (5 reviews)
Author: majiayu000

Fresh Eyes Review

Use before git commit, before PR creation, before declaring done - mandatory final sanity check after tests pass; catches SQL injection, security vulnerabilities, edge cases, and business logic errors that slip through despite passing tests; the last line of defense before code ships

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Fresh-Eyes Review

Core Principle

The central mandate is uncompromising: "NO COMMIT WITHOUT FRESH-EYES REVIEW FIRST"

This represents a final quality gate executed after implementation completion, passing tests, and peer review. The discipline applies universally, even without explicit skill activation.

Key Distinctions

Fresh-eyes review differs fundamentally from testing and code review:

Testing validates expected behavior under controlled conditions
Code review examines patterns and quality during implementation
Fresh-eyes catches unexpected issues through deliberate re-reading with psychological distance

The skill emphasizes that "100% test coverage and passing scenarios" can coexist with "critical bugs" waiting discovery.

Required Process

Step 1 - Announce Commitment Explicitly declare: "Starting fresh-eyes review of [N] files. This will take 2-5 minutes." This announcement creates accountability and reframes your mindset.

Step 2 - Systematic Checklist Review all touched files for:

Security vulnerabilities (SQL injection, XSS, path traversal, command injection)
Logic errors (off-by-one boundaries, race conditions, null handling)
Business rule implementation (calculations match requirements?)
Input validation (type, range, format checks complete?)
Performance issues (N+1 queries, unbounded loops)

Step 3 - Fix Immediately Address findings before declaring completion. Re-run tests after corrections.

Step 4 - Declare Results Mandatory announcement: "Fresh-eyes complete. [N] issues found and fixed." Include this even for zero findings—it proves execution.

Time Commitment

Expected duration: 2-5 minutes depending on file count. Faster completion suggests insufficient depth; excessive time indicates scope creep.

Resistance Patterns to Reject

The document explicitly lists rationalizations to ignore:

"Tests are comprehensive"
"I'm confident it's correct"
"Partner is waiting"
"Production is blocked"
"Senior dev already approved"

These circumstances represent precisely when critical bugs escape into production.

---name: fresh-eyes-reviewdescription: Use before git commit, before PR creation, before declaring done - mandatory final sanity check after tests pass; catches SQL injection, security vulnerabilities, edge cases, and business logic errors that slip through despite passing tests; the last line of defense before code ships--- # Fresh-Eyes Review ## Core Principle The central mandate is uncompromising: **"NO COMMIT WITHOUT FRESH-EYES REVIEW FIRST"** This represents a final quality gate executed *after* implementation completion, passing tests, and peer review. The discipline applies universally, even without explicit skill activation. ## Key Distinctions Fresh-eyes review differs fundamentally from testing and code review: - **Testing** validates expected behavior under controlled conditions - **Code review** examines patterns and quality during implementation - **Fresh-eyes** catches unexpected issues through deliberate re-reading with psychological distance The skill emphasizes that "100% test coverage and passing scenarios" can coexist with "critical bugs" waiting discovery. ## Required Process **Step 1 - Announce Commitment** Explicitly declare: "Starting fresh-eyes review of [N] files. This will take 2-5 minutes." This announcement creates accountability and reframes your mindset. **Step 2 - Systematic Checklist** Review all touched files for: - Security vulnerabilities (SQL injection, XSS, path traversal, command injection) - Logic errors (off-by-one boundaries, race conditions, null handling) - Business rule implementation (calculations match requirements?) - Input validation (type, range, format checks complete?) - Performance issues (N+1 queries, unbounded loops) **Step 3 - Fix Immediately** Address findings before declaring completion. Re-run tests after corrections. **Step 4 - Declare Results** Mandatory announcement: "Fresh-eyes complete. [N] issues found and fixed." Include this even for zero findings—it proves execution. ## Time Commitment Expected duration: 2-5 minutes depending on file count. Faster completion suggests insufficient depth; excessive time indicates scope creep. ## Resistance Patterns to Reject The document explicitly lists rationalizations to ignore: - "Tests are comprehensive" - "I'm confident it's correct" - "Partner is waiting" - "Production is blocked" - "Senior dev already approved" These circumstances represent *precisely when* critical bugs escape into production.

Frequently asked questions