standards-sync ยท diff
git:20261108.afae521 to git:20261115.d0ef121
1 added, 0 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: standards-sync
description: 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 the standards CLI.
---
# 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 `standards check` reports it as drift against `sync-standards.lock`. So before editing, find which class the path belongs to.
A consumer receives one of two payloads, chosen by `"payload"` in `sync-standards.local.json`. `core` holds `AGENTS.md`, the language-neutral skills, and the weekly sync, for a repository of any language. `bun`, the default, adds the Bun workspace tooling. A Bun consumer runs the CLI as `bun standards <command>`, any other as `bunx @davidvornholt/standards <command>`, which needs Bun installed but not a Bun workspace.
| Class | How to recognize it | Where a change goes |
| --- | --- | --- |
| Synced | `AGENTS.md`, or listed in a payload of `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 `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` | Below its `## Project-specific rules` heading |
| `justfile` and `secrets.just` | `local.just` |
| `.github/settings.json` | `.github/settings.local.json` |
| `.github/dependabot.yml` | Below its `# Project-specific updates` line |
| `.agents/skills/*` | Unmanaged sibling skill directories |
| `.github/workflows/standards-sync.yml` | `sync-standards.local.json` |
| `.mise/config.toml` | `mise.toml` |
| `nix/standards-bun.nix` and `nix/bun-archives.json` | `flake.nix` and `dev-shell.local.nix` |
+ | `nix/package-source.nix` and `nix/package-source-check.nix` | `flake.nix` and `nix/package.nix` |
A core consumer has only the `AGENTS.md`, skills, and sync workflow rows. An extension adds to its canonical file and doesn't replace it. GitHub settings can only add stricter settings, rulesets, and labels. A repository's own Dependabot blocks can't repeat a shared block's ecosystem, directory, and target branch, so a hold on a shared block goes upstream. Blocks that share an ecosystem and target branch list their directories without globs, because `check` can't tell whether two globs overlap.
`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](references/github.md).