agentleFS
Sign inStart free
Yeachan-HeoYeachan-Heo/oh-my-claude-sisyphus/skills/maintain-verification-skill/SKILL.md

maintain-verification-skill

Skill41k starsChanged 4 days agoMITView on GitHub

Re-sync the project's verification skill when its commands drift — re-run each recorded command, update expectations and the feature map to what is true now, record the verdict actually earned.

68 other projects use a version of this.

Trending

Quiet since January.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 3 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Yeachan-Heo/oh-my-claude-sisyphus repository that our weekly crawl found: only 3 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Yeachan-Heo/oh-my-claude-sisyphus

The biggest 3 of 3 mentions linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use setup-pstack, poteto-help and 3 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.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 19 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 27 projects that use this

  • JoshueOsunaSkill

    Poteto Mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 2

    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:

    after a toolchain or CI migration

    line 25
  2. Distinctive:

    If the project's verification has outgrown the single skill shape (multi- package, per-app checks), say so and split per surface rather …

    line 57

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

Maintain Verification Skill

A verification skill that names dead commands is worse than none: it fails loudly on trivia and passes quietly on what matters. This skill re-syncs the project's verify skill to the repo's current reality.

When to use

  • verification errors on a command that no longer exists or was renamed
  • a new surface (package, app, e2e suite) has no check recorded
  • after a toolchain or CI migration

Workflow

  1. Audit the recorded skill: list every command and manual check it names; for each, does the command still exist and still mean the same thing (flags, scripts, config)?
  2. Re-run, don't re-read: execute each surviving command and compare the observed outcome to the recorded expectation. A command whose passing shape changed gets its expectation rewritten, with the new evidence.
  3. Find uncovered surface: what does the repo build/check now that the feature map does not mention? Add the check by running it, or record the gap as uncovered — the map stays honest.
  4. Update the skill and feature map in place: same file, corrected commands, corrected coverage table, dated revision line at the top.
  5. Record the resync through the ledger's locked writer — appendLedgerEntry and defaultLedgerPath from the installed package's dist/features/verification-ledger/index.js (babysit's ledger step demonstrates the exact invocation); never append raw rows to .omc/state/verification-ledger.tsv — the writer owns header creation, locking, and cell sanitization. The verdict is the one the rerun actually earned — unit-test-verified when the test suite ran, live-ui-verified for a live-UI flow, type-check-only when only build/lint/typecheck commands were rerun — and those commands as evidence. Never claim a test ran that did not.

Rules

  • The rerun is the resync; nothing is marked current without execution.
  • Coverage that shrank is reported out loud, not silently dropped from the map.
  • If the project's verification has outgrown the single skill shape (multi- package, per-app checks), say so and split per surface rather than fattening one file.

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