agentleFS
davidvornholtdavidvornholt/mailbox/.agents/skills/review/SKILL.md

review

Skill2 starsChanged yesterdayMITView on GitHub

Use when asked for a read-only review of code, documentation, configuration, or workflows.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • +3 more from dzhng
  • +5 more from Lambenthan

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 3

    Distinctive

    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:

    If you're assigned one kind of failure, check everything that could fail that way and report nothing else.

    line 12
  2. Distinctive:

    Leave out anything you refuted or that isn't worth doing.

    line 20
  3. Distinctive:

    If you have no findings, say what you checked.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “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

Review

Review the change without editing it, so that someone can decide whether to merge it. Read the whole diff against the base you were given. If you need to change files to test something, do it in a disposable worktree. If you were given a gate result, don't rerun the gate.

Report a problem only when you can show how it would happen, from something you read or ran. Judge how much it matters against the stated intent, usually the pull request's description. Breaking a repository rule is evidence, not a blocker by itself.

If you're assigned one kind of failure, check everything that could fail that way and report nothing else.

Give each finding its file and line, what goes wrong, and one label:

  • block: you showed it can happen, and it's bad enough to stop this merge.
  • defer: it's real, but it shouldn't stop this merge. Say whether someone would run into it.
  • ask: only a person can choose, because the options are durable product or architecture directions that are expensive to reverse.

Leave out anything you refuted or that isn't worth doing.

Recommend the smallest fix and a regression test that fails without it.

Quote any documentation or comment that breaks the documentation rule under Cuts. A cut doesn't block, but it gets made before the merge. Text that would lead a reader into a real failure, such as a wrong command, is a finding instead.

If you have no findings, say what you checked.

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.