mirror of
https://github.com/mattpocock/skills.git
synced 2026-09-13 02:48:06 +07:00
chore: sync the plugin version from package.json on release
`npm run version` now runs `changeset version` and then `scripts/sync-plugin-version.mjs`, which copies the new version into `.claude-plugin/plugin.json`. The release workflow calls `npm run version` instead of `npx changeset version`, so the version PR carries both files. Also closes the drift this replaces: `plugin.json` was manually bumped to 1.2.1 while `package.json` stayed at 1.2.0. `package.json` moves up to 1.2.1 so the plugin version never goes backwards. `npm run check-plugin-version` reports drift without writing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
07999e06b5
commit
f3554acafe
@@ -8,7 +8,7 @@ Skills are organized into bucket folders under `skills/`:
|
||||
|
||||
Every skill in `engineering/` or `productivity/` (the **promoted** buckets) must have a reference in the top-level `README.md` and an entry in `.claude-plugin/plugin.json`'s `skills` array (the Claude Code plugin ships exactly the promoted set). Skills in `misc/`, `in-progress/`, and `deprecated/` must not appear in either.
|
||||
|
||||
Install commands are copied verbatim from [.agents/install-block.md](./.agents/install-block.md). `.claude-plugin/marketplace.json` makes the repo its own single-plugin marketplace — a fallback the install block explains, not the documented route. When bumping the release version, keep `.claude-plugin/plugin.json`'s `version` in sync with `package.json`'s — Claude uses the plugin `version` to decide when installed users see an update. Run `claude plugin validate . --strict` after touching either manifest. Why a Claude plugin but not (yet) a Codex one lives in [.agents/adr/0002-ship-as-a-claude-code-plugin.md](./.agents/adr/0002-ship-as-a-claude-code-plugin.md).
|
||||
Install commands are copied verbatim from [.agents/install-block.md](./.agents/install-block.md). `.claude-plugin/marketplace.json` makes the repo its own single-plugin marketplace — a fallback the install block explains, not the documented route. Run `claude plugin validate . --strict` after touching either manifest. Why a Claude plugin but not (yet) a Codex one lives in [.agents/adr/0002-ship-as-a-claude-code-plugin.md](./.agents/adr/0002-ship-as-a-claude-code-plugin.md).
|
||||
|
||||
Each skill entry in the top-level `README.md` must link the skill name to its `SKILL.md`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user