documentation-sync
Skill1 starsChanged 59 days agoMITView on GitHub
Update affected project knowledge after verified changes while preserving manual documentation.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- BurakD/ai-engineering-harnesstheir own version, first seen Nov 1, 2026
- volantlabs/vellistheir own version, first seen Oct 25, 2026
- dss-time/repo-doctor-skillstheir own version, first seen Oct 15, 2026
- homarr-labs/homarrtheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- homarr-labs/homarr★ 5.4ksame name
- volantlabs/vellis★ 9same name
- BurakD/ai-engineering-harness★ 1same name
- dss-time/repo-doctor-skills★ 1same 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 repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- content-safetySkill
- context-compactionSkill
- coordinator-communicationSkill
- cortex-controlSkill
- design-frontend-designSkill
- design-impeccableSkill
- design-reference-analysisSkill
- design-ui-ux-pro-maxSkill
- design-visual-qaSkill
- design-workflowSkill
- knowledge-harvest-scopeSkill
- knowledge-harvestSkill
- orchestratorSkill
- requirements-intakeSkill
- skill-authoringSkill
- skill-managementSkill
- tool-disciplineSkill
- tool-discipline-workerSkill
- worker-accessibility-auditorSkill
- worker-accessibility-fixerSkill
- worker-architectSkill
- worker-backend-devSkill
- worker-build-verificationSkill
- worker-code-reviewerSkill
- worker-database-architectSkill
- worker-data-engineerSkill
- worker-debuggerSkill
- worker-devops-engineerSkill
- worker-explorerSkill
- worker-frontend-devSkill
- worker-fullstack-devSkill
- worker-generalSkill
- worker-mobile-devSkill
- worker-performance-engineerSkill
- worker-plannerSkill
- worker-qa-engineerSkill
- worker-refactorerSkill
- worker-security-auditorSkill
- worker-senior-consultantSkill
- worker-technical-writerSkill
- worker-ux-designerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
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 41
Read applicable indexes and linked pages for the assigned scope.
- Distinctive: line 44
Update durable knowledge, public guidance and examples only where affected.
- Distinctive: line 47
Use an optional declared Markdown example only when it resolves a real content question.
- Distinctive: line 54
Do not add a reviewer assignment to the plan.
“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
Documentation synchronization
Responsibility
| Role | Work |
| Coordinator | Assess documentation impact and assign affected paths with the implementation or as independent work |
| Assigned implementing worker or technical writer | Apply this skill, confirm source-backed facts and update only affected documentation |
| Runtime's mandatory independent review | Check material documentation claims against source, commands and links |
The coordinator may inspect bounded project source, report evidence and public artifacts read-only to reconcile cited revisions and decide scope. Workers own project edits and checks; the coordinator does not rerun project checks. A stale or absent index does not automatically require harvest. The coordinator source-read restriction in knowledge-harvest applies only to harvests, not ordinary work.
The worker assigned the affected documentation applies this skill. The
coordinator does not read another role's SKILL.md.
For ordinary completion, include related documentation in the implementing worker's assignment when practical. Use a separate technical writer when the documentation is independent work or needs distinct ownership. Supported impact requires the affected updates and proportionate verification before acceptance; a supported no-impact conclusion needs no token edit or extra worker. If inspection is incomplete, gather bounded missing evidence or leave the impact unresolved.
Inputs for the assigned worker
- Verified behavior, architecture, interface, command or ownership changes.
- Exact affected index/page paths, requirements and preservation boundaries.
- Relevant reports, source routes and known uncertainties.
Work sequence
- Read applicable indexes and linked pages for the assigned scope.
- Confirm consequential claims in source, tests or executable configuration.
- Preserve manual material outside generated blocks unless its change is authorized.
- Update durable knowledge, public guidance and examples only where affected.
- Validate changed links, anchors, commands, terminology and stated behavior.
- Publish an ordinary Markdown report using the live draft creator's guidance. Use an optional declared Markdown example only when it resolves a real content question. Standard skill/reference reads do not authorize reading manifests, databases or other runtime internals.
Verification and completion
- The runtime's mandatory review checks material claims; list them in your report. Do not add a reviewer assignment to the plan; no special publication kind exists.
- A supported no-impact conclusion can use existing evidence without a token edit or extra worker.
- Missing inspection is not proof of no impact. State unverified facts and unrun checks.
- Required updates and their verification must finish before task completion.
- Record findings and follow-up in your report as unresolved; the pipeline is runtime-owned and the coordinator decides the next action from your report.
- Harvest already owns its documentation work; do not duplicate it under another label.
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.

