agentleFS
Sign inStart free
LucaDominiciLucaDominici/arbiter/.claude/skills/verification/SKILL.md

verification

Skill0 starsChanged 56 days agoApache-2.0View on GitHub

Use before claiming work is complete, before committing, or before creating PRs. Verify tests pass, gate passes, and no invariants are violated.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use evidence-driven-writing, experiment-results-planning 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.
  • Norman-burySkill

    evidence-driven-writing

    Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims

    Also in 3 projects that use this

  • Norman-burySkill

    experiment-results-planning

    Use when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final

    Also in 3 projects that use this

  • +10 more from Norman-bury

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 1

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

    Run this sequence before any completion claim — a claim made from memory of green output is the single most common agent failure mode, so …

    line 16
  2. Very specific:

    Commit and push only when every box above is checked.

    line 62

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

Verification Before Completion

Run this sequence before any completion claim — a claim made from memory of green output is the single most common agent failure mode, so every claim below is re-verified against the tree now, not recalled. Work through the steps in order; each depends on the previous one, and an unchecked box is an unfinished task, not an optional extra.

Checklist

1. Tests

npm run test
  • All tests pass
  • No skipped or disabled tests added
  • New behavior has test coverage

2. Quality Gate

node scripts/check-all.mjs L1
  • Typecheck passes
  • Lint passes
  • Format passes
  • No orphan TODOs

3. Invariant Check

  • No any types introduced
  • No disabled/placeholder tests

4. Before Push

node scripts/check-all.mjs preflight
  • Coverage threshold met
  • No dead code
  • No circular dependencies
  • CI full gate is green on the pushed SHA; record it with node scripts/ci-receipt.mjs

Stop conditions

Commit and push only when every box above is checked. A failing gate, a failing test, or a TODO without a task ID (TODO(#NNN): ...) stops the completion claim here: fix the root cause first — a claim made over a red check is false the moment it is written, and the Stop hook (INV-114) will reject it anyway. Report what is red and what you are doing about it instead of claiming done.

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