definition-of-done
Skill23 starsChanged 4 months agoApache-2.0View on GitHub
The ordered finish-line runner for any change in this repo — generators, then the asset-integrity refresh last on its own, then the full gate suite, then commit and push; use before declaring any change finished or whenever the stop hook reports uncommitted or untracked changes.
- Commits and pushes
10 other projects use a version of this.
Adopted by
Most recently taken up by
- khgouldy/skillstheir own version, first seen Nov 1, 2026
- scoobydont-666/shared-claude-skillstheir own version, first seen Nov 1, 2026
- musterd-io/musterdtheir own version, first seen Nov 1, 2026
- google/skills_lint.darttheir own version, first seen Oct 30, 2026
- phanijapps/memextheir own version, first seen Oct 17, 2026
- precise-alloy/ritustheir own version, first seen Oct 11, 2026
Used with
Projects with it also use tdd.
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.
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- google/skills_lint.dart★ 8same name
- PapyGaragos/skills★ 2same name
- kane-mar/skills★ 1same name
- khgouldy/skills★ 1same name
- musterd-io/musterd★ 1same name
- nandanosql/all_in_one_pm_skills★ 1same name
- precise-alloy/ritus★ 1same name
- scoobydont-666/shared-claude-skills★ 1same name
- Abdox-menara/guard-skills★ 0same name
- phanijapps/memex★ 0same name
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 repository15 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- catalog/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- mcp/AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- schemas/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agentic-delegationSkill
- model-registry-refreshSkill
- pr-babysitSkill
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 8 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
- Distinctive: line 17
Before declaring any change in this repo finished.
- Distinctive: line 42
Always, in this order:
- Very specific: line 56
Run integrity from the repo root — a leftover cd into tools/vfa-tui makes the write silently target a nonexistent path.
- Very specific: line 59
Never edit catalog/asset-integrity.json by hand.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Definition of Done
Doctrine
The order is load-bearing. The integrity manifest must hash the settled tree, so
asset-integrity:write always runs last, on its own, from the repo root — never folded into a
parallel generator batch, never run from a subdirectory.
Trigger
- Before declaring any change in this repo finished.
- Whenever the stop hook reports uncommitted or untracked changes.
Input
The list of paths you touched in this change.
Decision matrix
Pick the steps that apply based on what changed — most changes trigger more than one row.
- catalog / agents / skills / roles / providers changed →
npm run manifest:write:all, then re-run asset-integrity LAST on its own (the parallel-generator ordering caveat inCLAUDE.md). skills/**changed →npm run manifest:write.catalog/model-policy.jsonormodel-registry.jsonchanged →npm run model-policy:check(andmodel-policy:applyif the projection changed).tools/vfa-tui/**changed →cd tools/vfa-tui && cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo test. Return to the repo root afterwards — a persistedcdhas broken integrity runs before.- any root file /
agents//plugins//package.jsonchanged → asset-integrity refresh required.
The invariant sequence
Always, in this order:
- Applicable generators from the decision matrix above.
python3 tests/validate-asset-integrity.py --writefrom the REPO ROOT, last, on its own.npm run validate— zero failures.npm run lint:spellandnpx --yes markdownlint-cli2 "**/*.md" "#node_modules"— zero failures.git statusclean after committing with a scoped conventional-commit message.git push -u origin <branch>(retry with backoff on network errors only).
Footguns
grep -cE 'FAIL|ERROR'exits 1 on a count of 0 — do not chain it with&&before the commit, or a clean gate run looks like a failure and blocks you.- Run integrity from the repo root — a leftover
cdintotools/vfa-tuimakes the write silently target a nonexistent path. - Warnings from model-policy are exit-0 by design — read them, don't treat them as failures.
- Never edit
catalog/asset-integrity.jsonby hand.
Output
The checklist above with pass evidence per step, then the commit hash and push confirmation.
Delegation note
Gate runs may be delegated to a Haiku subagent per agentic-delegation's "Gate run" workflow
template, but the orchestrator reads the results and owns the commit — a delegate's self-report
that gates passed is not verification.
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.

