---
name: fresh-eyes-review
description: Use before completing substantial work, readying a branch or PR for review, or handling review findings.
title: fresh-eyes-review
canonical_url: https://skilld.dev/gh/bydradev/gh-repo-bootstrapper/fresh-eyes-review
last_updated: 2026-11-20T10:05:01.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install bydradev/gh-repo-bootstrapper/fresh-eyes-review`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/fresh-eyes-review`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/bydradev/gh-repo-bootstrapper/fresh-eyes-review) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/fresh-eyes-review`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/fresh-eyes-review --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/fresh-eyes-review --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Independent fresh-eyes review

For substantial work, use a different agent or person from the implementer.
Review each substantial phase before completion and the whole change before
declaring the branch or PR ready. One review serves both when it covers the
whole change at the proposed base and head for the same requested outcome.
Get an independent follow-up on later material changes, including review
fixes. A small edit that leaves the assessment valid needs no new round.
For rebases and other follow-ups, apply `review-guidelines`.

Prefer a stronger reasoning model and, where practical, another model family.
Give the reviewer the requested outcome, requirements, diff or changed files,
base and head commits, and validation results. For follow-ups, include the last
report and subsequent commits. The reviewer assesses the evidence independently
using `review-guidelines` (`.agents/skills/review-guidelines/SKILL.md`).

## Handling findings

These rules apply to the findings of every review, whoever started it. Treat
review findings as unverified until assessed against the repository and the
requested outcome: a finding is a claim, whatever its source or severity.

- Reproduce or trace each finding on the current code before changing
  anything.
- If it holds, fix the root cause, check similar code elsewhere, and, where
  practical, add a test that fails without the fix. Reply with the finding's
  ID, the commit, and how you checked it.
- If it does not hold, reply with the ID and the evidence, such as the guard,
  the test or the documented trade-off. Never change code just to satisfy a
  reviewer.
- If a fix would cost more than the risk it removes, say so. You may decline a
  P2 or P3 with that reason; a P0 or P1 is the operator's to accept or defer.
- Severity is the reviewer's estimate: dispute it with evidence, never quietly
  downgrade it.

Resolve valid blocking findings before completion or PR readiness.
`review-guidelines` defines which P0 and P1 findings block.

After three review rounds with blocking findings still open, stop and escalate
to the operator rather than starting another round: list the open findings,
what each round changed, and your recommendation.

OpenCode's free-tier models on its own provider currently refuse an agent whose
shell is denied, as this repository's OpenCode reviewer's is, with "can only be
used from within OpenCode" (OpenCode issue 49723, open on 2026-10-22). Run that
reviewer with another model or use another reviewer; don't loosen its
permissions.

## Cross-family review recipe

This recipe works in any harness. Save the diff, the requested outcome, the
relevant requirements, and the validation results to the session's scratch
directory (see the
`worktrees-and-scratch` skill). Save the base branch's `review-guidelines`
there too, or the head copy when the base branch has none, since a change can
edit the skill that reviews it. Write the reviewer prompt to a file there,
telling the reviewer to follow that saved copy instead of the worktree's, then
run the reviewer read-only from inside a git worktree:

```sh
git diff <base>...HEAD > <scratch>/review.diff
if git cat-file -e <base>:.agents/skills/review-guidelines/SKILL.md 2>/dev/null; then
  git show <base>:.agents/skills/review-guidelines/SKILL.md
else
  cat .agents/skills/review-guidelines/SKILL.md
fi > <scratch>/review-guidelines.md
codex exec --sandbox read-only --ephemeral -o <out> - < <prompt>
```

When the implementer is Codex, use another installed harness in read-only mode
instead, such as `claude -p`, the Antigravity CLI, or OMO. Read `<out>`, assess
each finding as *Handling findings* says, and delete the scratch files when the
review is done.
