done
Skill6 starsChanged 3 months agoMITView on GitHub
Run the closeout ritual before handing back non-trivial work; full verification, revert-probe honesty, independent review, and scope reporting. Use before declaring completion, opening a PR, wrapping up a change, or "ปิดงาน".
37 other projects use a version of this.
Adopted by
Most recently taken up by
- spongetimblin/claude-skill-librarytheir own version, first seen Nov 8, 2026
- vtmocanu/skillstheir own version, first seen Nov 7, 2026
- Melvynx/ai-maxxing-skillstheir own version, first seen Nov 1, 2026
- duthaho/skillhubtheir own version, first seen Oct 31, 2026
- bholmesdev/skillstheir own version, first seen Oct 18, 2026
- cyrilichti/agent-workflowstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use simplify, work and 4 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.
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 5 projects that use this
vbrevikSkillwork
Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.
Also in 3 projects that use this
OpenAISkilltranscribe
Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 9 projects that use this
genomewalkerSkilllearn
Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 4 projects that use this
Other versions37 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 37
- bholmesdev/hubble.md★ 1.5ksame name
- bholmesdev/skills★ 179same name
- Melvynx/ai-maxxing-skills★ 32same name
- endlessblink/master-plan★ 26same name
- fredoliveira/agents★ 24same name
- oldwinter/skills★ 11same name
- duthaho/skillhub★ 9same name
- Trejon-888/ix-claude-code-starter-kit★ 9same name
- HaipingShi/coderail★ 8same name
- ManceRayder42/jarvis-os★ 5same name
27 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- bisectSkill
- debugSkill
- discipline-reportSkill
- experimentSkill
- imouto-modeSkill
- lucia-busSkill
- lucia-chatSkill
- lucia-relaySkill
- planSkill
- readySkill
- retroSkill
- showSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
No verify command exists → use /ready.
- Very specific: line 27
Only when the diff adds or changes tests, run node <this-skill-dir>/scripts/revert-probe.cjs "<verify-cmd>" [pre-fix-ref] aimed at those …
- Very specific: line 70
No hedging: report done only after every step passes.
“Common” is measured: kept by at least 6 in 10 of the 33 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.
Files
Done
1. Full verify
The full tier — verify-full when present, otherwise verify — must be
green after the last code edit. Run it only when no such result exists; an
older green does not count. Quote the shortest decisive line.
- Red → you are not here yet. Return to the loop.
- No verify command exists → use
/ready; do not claim done.
2. Skeptic diff pass
Re-read the final diff as a hostile reviewer. Check:
- Edge cases: empty, zero, unicode, boundaries, concurrency.
- Error paths: failures, missing files, dropped network, cleanup.
- Changed contracts: APIs, formats, schema, config, old consumers.
- Accidental content: unrelated files, debug code, secrets, loose pins.
- Test honesty: would changed tests fail if implementation is reverted?
Only when the diff adds or changes tests, run
node <this-skill-dir>/scripts/revert-probe.cjs "<verify-cmd>" [pre-fix-ref] aimed at those tests.
Exit 2 is UNASSESSABLE: report it as no proof, not
as a pass. Weakened checks are findings. Fix findings and repeat full verify.
3. Risk-routed independent review
Choose focus:
security: auth, permissions, input, paths, commands, secrets, endpoints.contract: public API/CLI, schema, config, migration, consumers.general: money, concurrency, resources, or a wide uncertain diff.
A small, well-understood diff with no routed risk stops after the skeptic
pass: no review is the default. Otherwise run one pass — the harness's
built-in review command when it exists, else one lucia-reviewer agent —
naming both security and contract when both apply; never two. Brief only
the base ref, focus, and changed files; conclusions anchor it.
Fix and re-verify every blocker or major, unless the user explicitly
accepts the named risk. A minor may be deferred only when reported.
4. Scope check
Re-read the original request. Every item is delivered, or named as left out with
a reason. Never drop scope silently. A bus task you claimed through
/lucia-bus must be completed or blocked, with its result published,
unless the user cancelled it.
5. Lessons
For a dead end, footgun, or disproved approach, run /retro. If unfinished
state must transfer, use /lucia-relay instead.
6. Report
Done: <what changed, one line>
Proof: <verify command> → <decisive line>
Not covered: <verification gap>
Left out: <scope omitted + reason, or nothing>No hedging: report done only after every step passes. Machine output mirrors the
same facts; blocked output uses "status": "blocked" and its failing line.
{
"status": "done",
"verify": {"command": "./test.sh", "exit_code": 0, "decisive_line": "PASS all checks green"},
"not_covered": "<verification gap>",
"left_out": "nothing"
}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
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.

