agentleFS
Sign inStart free
yokeloopyokeloop/yoke/skills/review/SKILL.md

review

Skill1 starsChanged 4 months agoMITView on GitHub

Finds problems in code, fixes them and produces a report. Used when the user writes "review", "code review", "find issues", "find bugs", "check code", "code analysis", "prepare a report", "what's wrong with the code".

192 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 157 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Report location: Write the report to .yoke/ai/<slug>/<slug>-review.md.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 157 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 code for a task, fix the problems worth fixing, and leave behind a report a human reviewer can act on. A standalone utility — run it whenever code needs a second pass, not only inside a larger flow.

The orchestrator drives the run: it talks to the user, dispatches sub-agents for analysis and for fixes, and pauses only twice — to choose which findings to fix, and to choose what happens next. Every other step runs to completion without asking.

Input

$ARGUMENTS — a task-slug or a path to a task-file. With no argument, determine the slug from the current branch or the latest .yoke/ai/*/ directory. This input contract is stable, so callers that pass a slug keep working.

Procedure

The full pipeline — scope resolution, the code-reviewer dispatch, finding classification, the fix loop, validation, and report assembly — lives in reference/review-procedure.md. Read that file and execute it end to end. The report follows the template in reference/review-format.md.

Rules

  • Standalone utility. Review runs on its own; it never assumes a larger flow around it.
  • Fix, then report. Findings the user accepts are fixed and committed; everything found — fixed or skipped — lands in the report.
  • Report location. Write the report to .yoke/ai/<slug>/<slug>-review.md.
  • Every fork is one question. For any decision — fix scope, next action — ask a single AskUserQuestion with the recommended option listed first.
  • Delegate the work. File edits, bash, and analysis go to sub-agents; each receives only its own data.
  • Read the git memory. Pull decision context from the affected files' commit history per ${CLAUDE_PLUGIN_ROOT}/skills/gca/reference/history-reading.md — a finding that contradicts a Constraint: or re-proposes a Rejected: approach must cite the commit it argues with.
  • Language: match the ticket/input language, or follow the project-level definition in CLAUDE.md / AGENTS.md.

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