doc-consistency
Skill2 starsChanged 5 months agoMITView on GitHub
Walk the doc-consistency sweep when a session makes a substantive edit to a draft or active planning/spec doc in markdowns/ (decision changed, shared value updated, section restructured), or on explicit /doc-consistency invocation. Not for typo fixes, status flips, or style/voice issues — those belong to mechanical gates.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- TheColliery/CoalLedgertheir own version, first seen Nov 8, 2026
- AndrewBrown-USDA/aigb-skills-usdatheir own version, first seen Oct 31, 2026
- dongsheng123132/doc-consistencytheir own version, first seen Aug 10, 2026
- wukun2005-gif/ai-skillstheir own version, first seen May 10, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- AndrewBrown-USDA/aigb-skills-usda★ 7same name
- TheColliery/CoalLedger★ 2same name
- wukun2005-gif/ai-skills★ 2same name
- dongsheng123132/doc-consistency★ 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- build-featureSkill
- refactor-extractSkill
- refresh-vendorSkill
- build-featureSkill
- doc-consistencySkill
- refactor-extractSkill
- refresh-vendorSkill
The file
Files
/doc-consistency
Substance lives in markdowns/protocols/doc-consistency.md.
Steps:
- Discriminate kickoff vs iteration per
auto-trigger-discriminator.md. Typo fixes, status flips, and style edits exit silently. Explicit/doc-consistencyinvocation bypasses. - State the semantic delta of the edit — what claim changed, what premise it may invalidate.
- Enumerate the sweep set: all
status: draft+status: activedocs; the edited doc itself, in full (sibling sections + summary surfaces — frontmatterdescription, intro, verdict/summary tables); every declared quoter (quotes:frontmatter or<!-- quotes: ... -->comment) of any changed value. - Read each enumerated doc and check it for dependent claims — restated values, descriptions of the changed mechanism, premises the change invalidates.
- Classify findings — contradiction / stale-but-harmless / unaffected. Fix contradictions in the same change-set; report anchored
file:lineperrubric-shared-anchors.md. - Check the handoff + escalation triggers. If a value moved doc → runtime, verify the value-authority handoff edit landed. If the same doc pair contradicts repeatedly or the sweep set has grown heavy, walk the protocol's escalation path (consolidate first; gate only if consolidation doesn't apply).
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.