agentleFS
Sign inStart free
BuddhiliveBuddhilive/buddhi-cli/.agents/skills/review/SKILL.md

review

Skill1 starsChanged 15 days agoMITView on GitHub

Closeout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 5 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.
  • 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

  • +5 more from Lambenthan

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 153 edited versions we read keep these.

  • 4

    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:

    Shape — [refactor-clean](../refactor-clean/SKILL.md): Run it first, while restructuring is cheap and before you audit a diff that's about …

    line 16
  2. Distinctive:

    Docs — [write-docs](../write-docs/SKILL.md): Update the docs this change touched.

    line 20
  3. Distinctive:

    When you enter a pass, read its skill — the rules live there, not here.

    line 30
  4. Distinctive:

    Stop when a full pass adds nothing.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 153 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

A finished change earns "done" only after three lenses pass: its shape, its diff, and its docs. Each has a specialist skill. This skill owns only what they can't — the order they run in, the loop between them, and one verdict.

Workflow

  1. Scope. Fix the diff under review and confirm it's substantive; skip the whole pass for trivial edits.
  2. Shape — refactor-clean. Run it first, while restructuring is cheap and before you audit a diff that's about to move.
  3. Diff — code-review. Audit the settled shape. A finding that forces a structural change sends you back to step 2, not onward.
  4. Docs — write-docs. Update the docs this change touched. Then trace the link chain from the root README down to each one: every link on the path still resolves, and the hub-to-leaf flow still reads in order.
  5. Report. One verdict across all three passes — what each found, what you changed, what you left and why. Done only when every pass is clean or resolved.

Rules

  • When you enter a pass, read its skill — the rules live there, not here.
  • Order governs presentation, not disclosure: surface a finding the moment you hit it, even when a later pass owns it.
  • Loop, don't cascade: a later fix that reopens an earlier pass returns there. Stop when a full pass adds nothing.

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.

Check your setup, free