← ClaudeAtlas

releaselisted

GitHub release creation for cc-foundry plugins: per-plugin tags, release notes as the changelog, post-merge publishing, and moving the released plugins' XERJ Corpus Hub pins. Invoke whenever task involves merging a pull request into master, releasing or publishing a plugin version, bumping plugin versions, writing release notes, or refreshing the Corpus Hub pins.
xobotyi/cc-foundry · ★ 23 · Code & Development · score 81
Install: claude install-skill xobotyi/cc-foundry
# Plugin Releases Every plugin version bump that lands on master ships with a GitHub release. The release notes are the plugin's changelog — there are no CHANGELOG.md files (see [ADR 1.5](/design-docs/adr/1.5-plugin-changelog.md)). A merged version bump without a release is an incomplete ship. ## Before the Push Run `vp run cli check --pre-push` and push only when it reports no error. It fails on a plugin whose shipped files changed since `origin/master` while its version did not — a change that never reaches an install, because Claude Code keys its plugin cache on the version. ## When to Release - After every merge into master, check the merged range for plugin version bumps; create one release per plugin whose version changed. - The user's authorization to merge covers release creation — do not ask a second time. - Repo-level changes that bump no plugin version (ADRs, root docs, the dev CLI in `src/`, CI, this skill) get no release. - Several plugins bumped in one merge → one release each. ## Identify What to Release 1. Find bumped plugins in the merged range: `git diff <old-origin-head>..origin/master -- '*/plugin.json'`. When the old head is unknown, compare each plugin's `plugin.json` version against its latest `<plugin>-v*` tag from `gh release list`. 2. For each bumped plugin, resolve: - the commit on master that changed its `plugin.json` version — the release target - the previous release tag `<plugin>-v*`, if any — the notes range and compare-l