claude-seed-synclisted

# Claude seed sync Surfaces drift between the toolkit's current seed docs and what was installed in this project, then proposes targeted edits. The CLI emits seed content. This skill diffs, reasons, and writes the proposal to a review file. It does not write target files until the user confirms. ## Guards - If the `canon` CLI is not on PATH, stop: `❌ canon CLI not found. Install the toolkit first.` - If no `.claude/` directory exists at the project root, stop: `❌ No .claude/ directory found. Run canon claude init first.` ## Step 1: read toolkit sources and the drift report Run both in parallel from the project root: ```bash canon claude seeds list --json 2>/dev/null canon sync --check . --json 2>/dev/null ``` Seeds emit an array of `{name, source, target, content}`, where `target` is the path relative to the project root where the file installs. Seeds are the whole subject. No standard installs into a project, so there is no installed copy to audit and nothing to reconcile against the corpus. A standard a session needs is read with `canon standards <name>`, which resolves against the copy inside the package. ### Narrow the set by attribution The report is what separates a file the project edited from one the toolkit moved on without it. Read `seeds.entries` for seed paths. Keep every seed regardless of state. `CLAUDE.md` is the file a project edits most, and its `drifted` verdict is the case this skill exists for. Read the `canon-cli` skill before naming a sync co