syncdocs
CLAUDE.md0 starsChanged 18 days agoMITView on GitHub
An Agent Skill package: markdown only. There is no package.json here and nothing in this repository executes. It teaches an agent to sync a repository's documentation with its code: every fact (version, dependency, command, structure, feature) re-read from the manifests, lockfiles, scripts and files, and the prose left alone. Keep the two straight: the commands in references/ (npm pkg get, git ls-files, git grep, the lockfile one-liner) run against the target repository whose docs are synced, not this one. The…
In this repositoryOne other file it gives its agents.
- syncdocsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 12
Keep the two straight: the commands in references/ (npm pkg get, git ls-files, git grep, the lockfile one-liner) run against the target …
- Very specific: line 43
The one-liners run: After editing one, run it against a repository of the kind it reads and record how in provenance.md.
- Distinctive: line 60
Plain punctuation, wrapped at 110 columns: No em-dashes, en-dashes, arrows, middle dots or smart quotes in prose or tables.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repository is
An Agent Skill package: markdown only. There is no package.json here and nothing
in this repository executes. It teaches an agent to sync a repository's documentation with its code: every
fact (version, dependency, command, structure, feature) re-read from the manifests, lockfiles, scripts and
files, and the prose left alone.
Keep the two straight: the commands in references/ (npm pkg get, git ls-files, git grep, the
lockfile one-liner) run against the target repository whose docs are synced, not this one.
The skill was written by the engineer who maintains it. references/provenance.md is the rationale layer:
what the audit of the earlier implementation, a single SKILL.md, fixed, what was kept deliberately, and
what was added and never exercised.
Structure
SKILL.md: entry point, loaded whole on every activation, so it stays between 130 and 160 lines, the closing index line aside. Frontmatter isnameanddescriptiononly, the description being the trigger surface; the body carries the pipeline diagram and the seam paragraph that stands in foradaptation.md, six critical facts, seven hard rules, the invocation table, the quick start, the reference directory and the closing index line.README.md: the human-facing front door, in the section order of the index's STANDARD.md: install, activation, file table, seven non-negotiables, Not this, contributing, footer.references/ground-truth.md,syncing.md,reporting.md,provenance.md: one topic each, loaded on demand.evals/:prompts.mdholds what a user types after installing, in their words. The fixture is an empty Next.js app with no stale docs, so prompt 1 carries them; prompt 2 names a public repository to clone. The checks only confirm the app was left intact and the notes carry the score. Every other file there is one eval run: measured frontmatter that is never edited, then the notes of the person who ran it. Add a prompt rather than rewording one that has results. The procedure is section 10 of the index's STANDARD.md..github/workflows/agent-eval.yml: the caller of the index's reusable eval workflow, copied verbatim from STANDARD.md and the same in every skill. Never edit it, and never add a trigger onpushorpull_request.
Editing conventions
- Code blocks name their destination or their target. The one-liners run in the target repository's root; say so where a block could be mistaken for one that runs here.
- The one-liners run. After editing one, run it against a repository of the kind it reads and record how
in
provenance.md. - Identifiers are shared across files. The three classes (accurate, stale, unverifiable), the report's
three lists (changed, verified accurate, flagged), the invocations
/syncdocs,/syncdocs checkand/syncdocs <path>, the commit messagedocs: sync documentation with codebase state, and the sibling skill namesbumpv,commitandcode-auditappear in several files. Change them in all or none. - Keep the three tables in sync with
references/: the reference directory and the quick start inSKILL.md, and the file table inREADME.md. Links are relative. - The hard rules and the non-negotiables move together: the seven hard rules in
SKILL.mdand the seven non-negotiables inREADME.mdstate the same seven things in the same order, and neither is ever presented as optional. - The odd-looking parts stay. Flagging rather than deleting a missing feature, keeping a doc's version
precision, never committing when nothing is stale: each has an entry in
provenance.md. Read it before simplifying. - Mark additions as additions. Anything not exercised in a run belongs under Added in
provenance.md. - Nothing is renamed by the target. The target's manifests, scripts and paths are read as they are; every name in this skill is its contract.
- Plain punctuation, wrapped at 110 columns. No em-dashes, en-dashes, arrows, middle dots or smart quotes in prose or tables; ranges are written "1 to 4".
- Commits follow Conventional Commits with no AI attribution trailers; releases follow the index's STANDARD.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

