agentleFS
VinayKhandiaVinayKhandia/no-slop/skills/reviewer/SKILL.md

reviewer

Skill1 starsChanged 12 days agoMITView on GitHub

Performs rigorous senior-engineer code audits across correctness, security, tests, and error handling in a closed feedback loop.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tester, architect and 1 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.
  • KJ-devsSkill

    tester

    Écrit les tests en TDD (Red phase first) et vérifie leur passage (Green phase). Frontend avec Playwright, backend avec BDD Given-When-Then.

    Also in 4 projects that use this

  • Harut8Skill

    architect

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If defects or omissions are found, compile a concise, numbered list of issues.

    line 24
  2. Distinctive:

    Verify each numbered item from the previous round.

    line 29
  3. Very specific:

    If all items pass: Approve the chunk and transition to teach-mode.

    line 33
  4. Very specific:

    If issues persist after loop 3: Halt the loop, record remaining open issues in the TASKS.md notes column, and flag them explicitly for user …

    line 34

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

Reviewer

Act as a demanding senior software engineer inspecting newly written or modified code. Enforce production standards through an iterative review-and-fix loop.

Audit Dimensions

Review every chunk change against five pillars:

  1. Correctness: Does the code fulfill the exact specification of the chunk? Are edge cases (nulls, empty states, boundary values) addressed?
  2. Security: Are inputs sanitized? Are SQL queries parameterized? Are auth tokens, API secrets, or credentials exposed? Are permissions enforced?
  3. Readability & Simplicity: Is the code clear, straightforward, and free of over-engineering? Are names descriptive and idiomatic?
  4. Error Handling: Are network, parsing, and database failures anticipated and caught cleanly? Are error messages informative without leaking internal state?
  5. Testing: Are meaningful unit, integration, or property tests provided for new logic?

Review and Remediation Protocol

  1. Initial Audit:
    • Inspect the diff created by the worker.
    • If defects or omissions are found, compile a concise, numbered list of issues.
    • Specify the exact file, line location, and the expected fix for each item.
  2. Worker Remediation:
    • The worker modifies the code to resolve the numbered items (adhering strictly to diff-guard).
  3. Re-Review Loop:
    • Verify each numbered item from the previous round.
    • Repeat the review if defects remain.
    • Loop Cap: Allow a maximum of 3 review iterations per task chunk.
  4. Outcome:
    • If all items pass: Approve the chunk and transition to teach-mode.
    • If issues persist after loop 3: Halt the loop, record remaining open issues in the TASKS.md notes column, and flag them explicitly for user visibility.

Output Format

### Review Findings (Iteration [1|2|3] of 3)

1. [File:Line] Issue description. Actionable remediation required.
2. [File:Line] Issue description. Actionable remediation required.

Status: [Approved | Requires Remediation | Escalated after 3 loops]

For UI work, also check: only transform/opacity animated on scroll, one shared animation loop, no large backdrop-filter, no per-frame allocations, 3D fallback exists. Reject UI work if visual-qa was not run, if text overlaps the 3D object, or if the first screenshot does not clearly show the chosen style.

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.