agentleFS
omdenkar2-uiomdenkar2-ui/all-in-one/skills/aio-doc-review/SKILL.md

aio-doc-review

Skill0 starsChanged 32 days agoMITView on GitHub

Review backend plans, API contracts and runbooks for contradictions, gaps and stale operational claims.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Read the exact document, its authority/source, intended consumers and referenced code/evidence.

    line 12
  2. Very specific:

    Check interface/state semantics, R/U/V coverage, source freshness, authorization, recovery/versioning and operational instructions against …

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

AIO Doc Review

Review backend plans, API contracts and runbooks for contradictions, gaps and stale operational claims.

Protocol

  1. Read the exact document, its authority/source, intended consumers and referenced code/evidence. Separate acceptance facts, design decisions and speculative recommendations.
  2. Check interface/state semantics, R/U/V coverage, source freshness, authorization, recovery/versioning and operational instructions against actual implementation or accepted design.
  3. Find concrete contradictions and missing decisions that affect execution. Prefer a precise correction over adding broad boilerplate or unsupported guarantees.
  4. Return actionable finding IDs, location/consequence and suggested edit. Apply document edits when authorized; document review does not substitute for runtime/code review.

Return and handoff

A document review or corrected artifact with resolved and outstanding material findings.

In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.

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.