spec-kit-canon

Claude skill entrypoint for grouping staged files into meaningful conventional commits. Use when Claude needs to inspect the staging area, cluster staged files by logical concern, propose a commit plan with messages and file lists, and apply that plan one group at a time without staging anything that was not already staged.

Group already-staged files from a bulk operation into meaningful commits and propose the message and file list for each commit. Use when a large batch of staged changes spans multiple logical concerns and must be split into well-scoped conventional commits before pushing. Only staged files are considered — unstaged changes are ignored.

Claude skill entrypoint for the shared Spec Kit Canon version bump workflow. Use when Claude needs to default to the next minor version in `extension/extension.yml` and `preset/preset.yml`, update the pinned release commands in `docs/INSTALL.md` and `docs/UPGRADE.md`, keep documented base Spec Kit versions aligned with `preset/spec-kit-release.json`, update `CHANGELOG.md` automatically from Conventional Commit subjects, bump only patch or major when that scope is explicitly requested, or apply an exact version only when the user explicitly provides one.

Claude skill entrypoint for syncing `preset/` with the latest released upstream `spec-kit` core commands. Use when Claude needs to verify the real latest release tag against `../spec-kit` `origin`, export the upstream release snapshot, rebase the regular upstream-tracking commands by preserving or intentionally retiring named `spec-kit-canon` overlay blocks, and manually merge the `speckit.constitution` and constitution template files.

Bump the shared release version in both publishable Spec Kit Canon manifests, update the version-pinned release commands in `docs/INSTALL.md` and `docs/UPGRADE.md`, keep any documented base Spec Kit version in sync with `preset/spec-kit-release.json`, and automatically update the repo changelog. Use when preparing the next release, aligning `extension/extension.yml` and `preset/preset.yml`, defaulting to the next minor version when the prompt just asks to bump the extension version, bumping only patch or major when that scope is explicitly requested, or applying an exact `X.Y.Z` or `vX.Y.Z` version only when the user explicitly asks for a specific version.

Sync `preset/` with the latest released upstream `spec-kit` core command sources. Use when rebasing `preset/commands/*.md` or `preset/templates/constitution-template.md` onto the newest upstream release tag, verifying the real latest release against `../spec-kit` `origin`, fetching a missing release tag locally, exporting upstream source snapshots, preserving or intentionally retiring canon-owned HTML comment overlay blocks in the regular upstream-tracking commands, handling the larger `speckit.constitution` merge, and keeping the visible upstream-baseline notes in the README files aligned with the recorded sync metadata.

Validate the local Spec Kit Canon extension and canon-core preset against the real sibling workspace layout (`spec-kit`, `spec-kit-canon`, `spec-kit-canon-test`). Use when starting or resuming the dedicated extension test workflow, optionally clearing `spec-kit-canon-test` before step 1, overriding the scaffolded Spec Kit script variant (`sh` vs `ps`) when needed, verifying constitution config rendering from the shared fixture, seeding the trivial canon, running the standard `/speckit.specify` to `/speckit.implement` workflow, exercising `/speckit.canon.drift` (with manual resolve and analyze gates) and `/speckit.canon.vibecode-drift` (with analyze gate before canonize), verifying that canon updates capture new API and web UI behavior, and generating a final Markdown test report with per-step results, test-run metrics, and developer-history copies in `spec-kit-canon/tests/history/`.

Claude skill entrypoint for the shared Spec Kit Canon extension test workflow. Use when Claude needs to start or resume the local extension validation run against the real sibling workspace layout (`spec-kit`, `spec-kit-canon`, `spec-kit-canon-test`), optionally clear `spec-kit-canon-test` before step 1, seed the trivial canon baseline, run the standard `/speckit.specify` to `/speckit.implement` workflow, exercise `/speckit.canon.drift` (with manual resolve and analyze gates) and `/speckit.canon.vibecode-drift` (with analyze gate before canonize), verify canon updates, and generate the final validation report.