agentleFS
Sign inStart free
elfrostelfrost/ai-patchlab/.agents/skills/review-code/SKILL.md

review-code

Skill1 starsChanged 30 days agoMITView on GitHub

Review the current diff or target files using EzProject quality rules. Use when the user asks for a code review, audit of recent changes, or a bug-risk-focused pass over modified files before merge or release.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use audit-test-suite, change-data-safely 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.
  • yaohuangguanSkill

    audit-test-suite

    Find where an existing test suite is weak and decide what to test next, ranked by risk. Use this when asked to add missing tests, find gaps, raise coverage, assess test quality or see which areas are thin, even if the request only mentions a coverage percentage.

    Also in 3 projects that use this

  • yaohuangguanSkill

    change-data-safely

    Change a database schema or stored data without breaking running code or losing data. Use this for any migration, new or changed column, backfill, bulk update, delete, index, or change to a stored format, including in small projects. Data mistakes are often impossible to undo.

    Also in 3 projects that use this

  • mrdulasolutionsSkill

    clear-caches

    Clear extension caches, analysis data, and drafts from the database. Use when testing sender lookups, analysis, or draft generation from a clean state.

    Also in 3 projects that use this

  • GeiserXSkill

    docs-loop

    Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.

    Also in 3 projects that use this

  • mrdulasolutionsSkill

    electron-devtools-testing

    Test the Electron app interactively using Chrome DevTools Protocol. Use when the user asks to test, verify, or interact with the running app via browser automation.

    Also in 3 projects that use this

  • GeiserXSkill

    full-loop

    Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.

    Also in 3 projects that use this

  • +1 more from mrdulasolutions
  • +4 more from GeiserX
  • +1 more from yaohuangguan

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 5

    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:

    Read CLAUDE.md if present for cross-runtime expectations.

    line 12
  2. Distinctive:

    Run lightweight validation when it materially supports the review.

    line 19
  3. Distinctive:

    Prefer concrete defects over style commentary.

    line 27
  4. Distinctive:

    If no findings are discovered, say so explicitly and mention residual risk or testing gaps.

    line 28
  5. Distinctive:

    Call out documentation drift when code changed but shared docs did not.

    line 29

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

Review changes with bugs, regressions, risks, and missing tests as the primary focus.

Workflow

  1. Read AGENTS.md.
  2. Read CLAUDE.md if present for cross-runtime expectations.
  3. Review the current git diff. If the user names files, review those too.
  4. Check:
    • correctness and regressions
    • missing validation or tests
    • pattern drift from examples/
    • documentation drift for ROADMAP.md, DECISIONS.md, AGENTS.md, CLAUDE.md, README.md
  5. Run lightweight validation when it materially supports the review.

Output

  • Findings first, ordered by severity, with file references
  • Open questions or assumptions
  • Brief summary only after findings

Rules

  • Prefer concrete defects over style commentary.
  • If no findings are discovered, say so explicitly and mention residual risk or testing gaps.
  • Call out documentation drift when code changed but shared docs did not.

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