agentleFS
ji-hun-gitji-hun-git/how-to-use-ai/skills/fresh-eyes-review/SKILL.md

fresh-eyes-review

Skill0 starsChanged 7 days agoMITView on GitHub

Reviews finished work as an independent reviewer who did not produce it. Use after drafting a document, plan, analysis or code change and before declaring it done; when the user asks for a final check, a second opinion or a review against a spec; or when the same session wrote the work and is about to grade it. Checks the result against the original requirements and evidence only, not against the conversation that produced it.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start clean: If you can, run this review in a new session or a subagent that has not seen the drafting conversation.

    line 13
  2. Distinctive:

    Check correctness, not style: Look for factual errors, unsupported claims, broken logic, failing or missing checks, security issues and …

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fresh-eyes review

Agents grading their own work skew positive, and a reviewer that watched the work being made inherits its blind spots. Separate the maker from the checker.

Steps

  1. Start clean. If you can, run this review in a new session or a subagent that has not seen the drafting conversation. If you can't, explicitly set aside the conversation and work only from the inputs below.
  2. Gather only:
    • the original request or spec (requirements, done criteria),
    • the final artifact (document, diff, data output),
    • the evidence (sources, test output, data).
  3. Check requirement by requirement. For each requirement or done criterion: met / partly met / not met, with the specific evidence (line, section, test output).
  4. Check correctness, not style. Look for factual errors, unsupported claims, broken logic, failing or missing checks, security issues and scope creep. Skip style preferences unless the spec asks for them.
  5. Report only what matters. List issues that would make the work wrong, unsafe or incomplete, each with a fix. If nothing significant is wrong, say "No significant issues" rather than inventing minor ones.
  6. Hand back the findings; let the original author (or the user) decide on fixes.

Evidence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.