fresh-eyes

Review recently changed code to identify bugs, edge cases, and readability problems.

69|11|Updated Dec 30, 2025

Search Tags:#readability #edge-cases #static-analysis #code-review #bug-detection #coding-best-practices

Ready to run

npx skills add https://github.com/richtabor/agent-skills --skill fresh-eyes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fresh-eyes
Source: https://github.com/richtabor/agent-skills/tree/main/skills/fresh-eyes
Command: npx skills add https://github.com/richtabor/agent-skills --skill fresh-eyes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-reads code you just wrote or modified with a fresh perspective to catch bugs, errors, and issues.

Core Features & Use Cases

Identifies logic errors, off-by-one mistakes, and edge cases in recently changed files.
Catches obvious bugs, typos, and confusing patterns without large refactors.
Provides concrete fixes and a concise summary suitable for immediate review.

Quick Start

Tell the AI to perform a fresh-eyes review on your latest code changes and suggest concrete fixes.

Frequently Asked Questions about fresh-eyes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I catch logic errors and edge cases in recently changed code before committing?▼

Perform a fresh-eyes code review on recently changed code to catch logic errors, edge cases, and readability problems before commit. It re-reads modified files with a new perspective and provides concrete fixes.

What is the best way to review code changes for bugs and readability issues across different file types?▼

The best way to review code changes for bugs across any file type is a structured fresh-eyes review. It locates changed files, re-reads them, documents off-by-one mistakes and confusing patterns, and outputs a concise summary with fixes.

Can I use automated code review to detect typos and confusing patterns without performing large refactors?▼

Yes, you can use a fresh-eyes code review to catch obvious bugs, typos, and confusing patterns without large refactors. It enforces a structured process to document issues and provides concrete fixes suitable for immediate review.

Does static analysis for bug detection work on any programming language and module?▼

Yes, fresh-eyes static analysis for bug detection works across any programming language, file type, or module. It analyzes recently changed files after feature completion, bug fixes, or major edits to identify logic errors and edge cases.

When do I need to perform a fresh-eyes review of my code?▼

You need to perform a fresh-eyes review after feature completion, bug fixes, or major edits. It re-reads your recently changed code with a fresh perspective to identify bugs, errors, readability problems, and edge cases.

Limitations of relying on code review for catching edge cases in modified files?▼

A limitation of fresh-eyes code review for catching edge cases is that it focuses on recently changed files and provides concrete fixes without large refactors, meaning pre-existing issues in untouched code may remain undetected.