docs-maintenance
Skill1 starsChanged yesterdayMITView on GitHub
Writes, updates and audits The Claude Factory's documents from their templates, such as each plugin's README.md, CHANGELOG.md, LICENSE and NOTICE.txt, the root README.md and CHANGELOG.md, and the root policy files (CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, PRIVACY). Use before and while creating, editing, reviewing or auditing any of these documents, and whenever another skill says to write a document with it, even for a one-line fix.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- OrionicsLtd/claude-skillstheir own version, first seen Nov 8, 2026
- OpenSelfHosting/skillstheir own version, first seen Oct 25, 2026
- anrysys/tg-aitheir own version, first seen Oct 20, 2026
- Seekers2001/docs-governancetheir own version, first seen Oct 13, 2026
- qshanx/docs-governancetheir own version, first seen Oct 13, 2026
- InternationalColorConsortium/iccDEVtheir own version, first seen Oct 8, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Seekers2001/docs-governance★ 320same name
- qshanx/docs-governance★ 253same name
- InternationalColorConsortium/iccDEV★ 187same name
- OpenSelfHosting/skills★ 2same name
- OrionicsLtd/claude-skills★ 1same name
- anrysys/tg-ai★ 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 repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- referencesSkill
- plugin-catalog-changesSkill
- plugin-iconsSkill
- plugin-releasesSkill
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 4 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
- Distinctive: line 34
Read governance.md in full: the values only the owner can give, the checks, and the conventions every document follows.
- Distinctive: line 37
Write the document, then run the checks in its procedure and in governance.md, and show their raw output.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Docs maintenance
Everything these documents say reaches third parties: a plugin's README tells a stranger what runs on their machine, a changelog tells them what an update breaks, and a license or a notice carries legal terms. Each document has a fill procedure and a template here, checked against the official sources, so that every document comes out the same way whoever writes it. Write each one from its procedure and its template, never from memory.
Who writes
- You write the documents, following the procedure and the template in the table below.
- The one exception is a plugin README written in full for the first time, such as a new plugin's: launch the
plugin-readme-writersubagent for it, because the README is long, has many rules, and benefits from its own context. Brief it as governance.md says. Where no subagent is available, as in a cloud thread of a Claude Project, write it yourself from the same procedure. - Versions, change types, renames, removals and releases are decided by the
plugin-releasesandplugin-catalog-changesskills. They call this skill for the documents they need; take their decisions as given.
Documents
| Document | Procedure | Template |
plugins/<plugin>/CHANGELOG.md | changelog.md | CHANGELOG-template.md |
Root CHANGELOG.md | marketplace-changelog.md | marketplace-changelog-template.md |
plugins/<plugin>/README.md | plugin-readme.md | plugin-readme-template.md |
Root README.md | root-readme.md | root-readme-template.md |
Root and plugin LICENSE | license.md | LICENSE-template.md |
plugins/<plugin>/NOTICE.txt | notice.md | NOTICE-template.md |
CODE_OF_CONDUCT.md | code-of-conduct.md | CODE_OF_CONDUCT-template.md |
CONTRIBUTING.md | contributing.md | CONTRIBUTING-template.md |
SECURITY.md | security.md | SECURITY-template.md |
SUPPORT.md | support.md | SUPPORT-template.md |
PRIVACY.md | privacy.md | PRIVACY-template.md |
How to write a document
- Read governance.md in full: the values only the owner can give, the checks, and the conventions every document follows.
- Read the document's procedure in full, then its template. Each procedure says what the document produces, its sources, what each placeholder means and where its true value comes from, its rules and its checks. When another skill called you for one task, apply the procedure step that matches it (for example, a release:
changelog.mdstep 4) and say which step you applied. - Take every value from the repository's files, the calling skill's decisions or the owner. Ask the owner for a value only the owner can give; never invent one.
- Write the document, then run the checks in its procedure and in governance.md, and show their raw output.
Events that call for documents
The changes the lifecycle skills handle (a plugin change, a new version, a rename, a removal, a withdrawn version) start from those skills. These other events start here; read the event's file and follow it:
| Event | It applies when | Reference |
| Repository foundation | The repository's own documents are created or rebuilt | repository-foundation.md |
| New plugin | A plugin directory with its plugin.json appears and is listed in marketplace.json | new-plugin.md |
| Third-party material changes | Another author's material is added to a plugin, updated or removed | third-party-material.md |
| Data handling changes | A plugin starts or stops calling a remote service, collecting data or keeping files on the user's machine | data-handling.md |
| The owner changes a policy | A copyright line, reporting channel, security policy, support channel or contribution process changes | policy-change.md |
| Audit or review | Someone asks whether the documentation is correct, or drift is suspected | audit.md |
| A small fix | A typo, a broken link or an outdated sentence | small-fix.md |
commands.md says what each documentation command checks and what it doesn't.
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.

