standards-sync
Skill2 starsChanged 9 days agoMITView on GitHub
Use when changing a file the standards sync manages (listed in `sync-standards.json`, such as `AGENTS.md`, `biome.base.jsonc`, `justfile`, canonical skills, or the standards workflows), changing sync behavior, propagating standards, or running `bun standards`. Routes each change to the owner that keeps it.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- davidvornholt/mail-mcpword for word, first seen Nov 5, 2026
- cordanaLLM/praetortheir own version, first seen Oct 14, 2026
Other versions2 projects use a version of this.
Word for word · 1
- davidvornholt/mail-mcp★ 2100% same
Edited · 0
None found.
Wrote their own version · 1
- cordanaLLM/praetor★ 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ci-pipelinesSkill
- databaseSkill
- declarative-infraSkill
- frontend-designSkill
- issuesSkill
- nextjsSkill
- prsSkill
- review-fixSkill
- reviewSkill
- screenshots-in-prsSkill
- secrets-and-configSkill
- ux-uiSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Before changing declared repository settings, the automatic sync workflow, or Standards auto-merge, read GitHub settings, automatic sync, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Standards sync
The canonical files live in davidvornholt/standards and are mirrored into every consumer repository. A consumer's copy of a synced file is read-only: the next sync overwrites any local edit, and bun standards check reports it as drift against sync-standards.lock. So before editing, find which class the path belongs to.
| Class | How to recognize it | Where a change goes |
| Synced | Listed in sync-standards.json, or inside a listed directory | The standards repository, which edits canonical files directly |
| Project-owned | Seeded once by init from template/, or an extension point below | The consumer, freely |
| Generated | Rebuilt by the CLI, such as .github/dependabot.yml and sync-standards.lock | Its inputs, then regenerate |
A change every consumer should get belongs upstream. A change for one consumer belongs in that consumer's extension point. Don't copy canonical logic into a project-owned file to change it locally.
Extension points
| Canonical path | Consumer extension |
biome.base.jsonc | biome.jsonc |
AGENTS.md | AGENTS.local.md |
justfile and secrets.just | local.just |
.github/settings.json | .github/settings.local.json |
.github/dependabot.base.yml | .github/dependabot.local.yml |
.agents/skills/* | Unmanaged sibling skill directories |
.github/workflows/standards-sync.yml | sync-standards.local.json |
.mise/config.toml | mise.toml |
nix/standards-bun.nix | flake.nix and dev-shell.local.nix |
An extension adds to its canonical file and doesn't replace it. GitHub settings can only add stricter settings, rulesets, and labels.
bun standards help lists the commands and options.
Before changing declared repository settings, the automatic sync workflow, or Standards auto-merge, read GitHub settings, automatic sync, and auto-merge.
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.