fresh-eyes

Fresh Eyes

Run a final whole-diff review pass with no session-history bias. This is a side-effect-free review primitive that uses the same output contract as review, but with a different posture: look across the entire change set after the obvious iterative fixes are done.

fresh-eyes may read files, inspect diffs, and classify findings. It must not edit files, commit, push, post comments, update tickets, create PRs, or run a fix loop. Callers decide what to do with the findings.

Use this for:

• Final pre-PR review from ready-for-review after the normal review loop
• A last-pass review after rinse has applied iterative fixes
• Checking a supplied patch for cross-file consistency and drift
• Catching baseline issues that hunk-by-hunk review missed

If the repo declares custom lifecycle hooks, read ../lifecycle-hooks.md and honor any phase-boundary hooks before and after fresh-eyes.

Do not use this for:

• The first local diff review — use review
• Interactive walkthroughs — use walk-the-diff
• Fixing review findings — return findings to the caller
• Posting PR comments — use pr-patrol

Process

1. Establish the input

Accept one of:

• Caller-supplied diff/range/context
• Local git diff against a base branch
• Pasted patch/diff

If reviewing local changes and the caller did not supply a range:

git status --short
gh pr view --json baseRefName,headRefName 2>/dev/null
git merge-base HEAD main  # or master / PR base when applicable
git diff <base-sha>...HEAD --stat
git diff <base-sha>...HEAD

If the base is unclear, ask once.

2. Load compact context only

Prefer context supplied by the caller:

• What changed and why
• Ticket/spec/design summary
• Verification already run
• Previous review findings that were fixed or accepted
• matching break_spec_approved, spec_approved, or blueprint_approved latest pointer entries when the ticket uses custom artifact locations

Do not rely on long conversation history. If context is missing, say so and review against general production readiness.