fresh-eyes

Reviews whole diffs for cross-file consistency, config drift, and pre-PR issues.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill fresh-eyes-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fresh-eyes
Source: https://github.com/sandsower/beislid/tree/main/skills/fresh-eyes
Command: npx skills add https://github.com/sandsower/beislid --skill fresh-eyes-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Iterative fix loops and hunk-by-hunk reviews often miss cross-file inconsistencies, config drift, stale documentation, and baseline compatibility issues that only appear when viewing the entire change set as one unit. ## Core Features & Use Cases - Whole-Diff Final Pass: Reviews the complete change set against a base branch or supplied patch, checking naming, data shapes, API consistency, error handling, and backward compatibility across all files. - Structured Review Contract: Outputs severity-classified findings (Critical, Important, Minor) with stable IDs, confidence levels, evidence, suggested fixes, and a merge verdict. - Side-Effect-Free Operation: Never edits files, commits, pushes, or posts comments; it returns findings to the caller for decision-making. - Use Case: After your review-and-fix loop converges, run a final fresh-eyes pass before PR handoff to catch stale docs, leftover debug code, and test blind spots introduced by incremental fixes. ## Quick Start Ask the agent to run a fresh-eyes review of the current branch diff against main before creating the pull request.

Frequently Asked Questions about fresh-eyes

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

FAQPage Schema
How do I run a final review of my whole diff before creating a PR?▼

Invoke fresh-eyes after your normal review and fix loop completes. It computes the diff against your base branch (or accepts a supplied patch), reviews the entire change set as one unit, and returns severity-classified findings with a merge verdict.

What is the difference between fresh-eyes and a regular code review pass?▼

A regular review works hunk-by-hunk during iterative fixes, while fresh-eyes examines the completed change set without session-history bias. It targets cross-file consistency, config drift, stale docs, and blind spots that incremental review misses.

Can fresh-eyes fix the issues it finds automatically?▼

No. Fresh-eyes is strictly side-effect-free: it cannot edit files, commit, push, post comments, or run fix loops. It returns findings to the caller, which decides whether to fix, accept, or escalate each issue.

What kinds of issues does a whole-diff review catch?▼

It catches cross-file naming and data-shape mismatches, environment variable and feature flag drift, pagination and timeout inconsistencies, backward compatibility breaks, stale READMEs and docs, dead code, and test blind spots from repeated small fixes.

When should I not use a fresh-eyes review pass?▼

Do not use it for the first local diff review, interactive diff walkthroughs, fixing findings, or posting PR comments. It is designed as a final gate after iterative review loops converge, not as an initial or interactive review tool.