Repository navigation
v1.8.0
One new rule for anyone who publishes skills or plugins through a marketplace: the branch it serves is production.
Changed: release-gate, any release
- The branch a plugin or skill marketplace serves is production. When a pack's source names a folder and no ref, installs read that branch's head (Claude Code, observed
2026-11-07). So a push to that branch is a release, whatever your tags say. - Keep the next release's work on its own branch. Move the served branch to the reviewed commit only at the go, so the tag names its head.
The receipt is this collection: two commits pushed after v1.6.1's tag reached auto-updated installs within the hour, before their review had finished. One of them was v1.7.0's skill rename. From now on, this repository works on next, and main moves only at a release.
What to do
- You publish a marketplace from a branch: work on another branch, and fast-forward the served one at each release's go.
44 skills in six packs.
Install: README § Install. Lost at any point? Type /product:start-here (Codex: $product:start-here) and say what you have.