oliver-kriska/release
| CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill release
Cuts a versioned release of the Elixir/Phoenix plugin. Drives the full
checklist from CLAUDE.md (Release + Versioning) so every release is
consistent. Contributor tooling — not shipped in the plugin.
make ci — the gate runs BEFORE committing. No green, no release.claude plugin tag — this is a marketplace layout (plugins/elixir-phoenix/.claude-plugin/plugin.json, not repo root). Tag manually: git tag vX.Y.Z.plugin.json version == CHANGELOG heading == git tag (vX.Y.Z). Verify before pushing.gh release create are outward-facing and hard to reverse. Stop and confirm with the user; show exactly what will be pushed/published first.plugin.json BUMP — never ship CHANGELOG/code changes without bumping the version, or installed users get nothing (cache).## [Unreleased] — one [Unreleased] becomes one version heading; re-add an empty one on top.git push --force is hook-blocked here. If history needs rewriting, the user runs it via !.main, working tree clean except intended release files. If feature work is uncommitted, commit it first.git describe --tags --abbrev=0 FIRST — the lastreleased tag is the bump base, NOT plugin.json (which may carry an
unreleased phased bump). If plugin.json is already ahead of the tag,
apply the consolidation check below before picking a number.
plugins/elixir-phoenix/.claude-plugin/plugin.json. Pick bump from ## [Unreleased] contents:plugin.json versionSet "version" in plugins/elixir-phoenix/.claude-plugin/plugin.json to X.Y.Z.
(Often already bumped during the feature work — confirm it matches the target.)
In CHANGELOG.md:
## [Unreleased] → ## [X.Y.Z] - YYYY-MM-DD (today's date).${CLAUDE_SKILL_DIR}/references/templates.md).README.md ONLY if counts/version callouts changed: skill count, agentcount (grep -nE "[0-9]+ (skills|agents|specialist)" README.md), or a version banner.
A pure doc/reference PATCH usually needs no README change — verify, don't assume.
plugins/elixir-phoenix/skills/intro/references/tutorial-content.md cheat sheetif commands/skills/agents were added, removed, or renamed.
make ciRun make ci (lint + test + validate + eval-all). Must be green. If lint trips on
untracked non-source dirs (e.g. social/, .rtk/), that is not a code failure — exclude
them, don't ship around real failures. See ${CLAUDE_SKILL_DIR}/references/templates.md.
git add CHANGELOG.md plugins/elixir-phoenix/.claude-plugin/plugin.json # + README if touched
git commit # message below
Commit subject (matches history): Release vX.Y.Z — <short summary>
End the message with the Co-Authored-By trailer (see CLAUDE.md).
git tag vX.Y.Z
Show the user the pending commit, tag, and release notes. On confirmation:
git push origin main
git push origin vX.Y.Z
gh release create vX.Y.Z --title "vX.Y.Z — <summary>" --notes-file <changelog-section>
Use the new CHANGELOG section as release notes (extract it to a temp file or --notes).
gh release view vX.Y.Z
git describe --tags --abbrev=0 # should print vX.Y.Z
Confirm to the user: released, tag pushed, GitHub release live.
${CLAUDE_SKILL_DIR}/references/templates.md — CHANGELOG/release-notes templates, gate snippets, gotchasTake oliver-kriska/release from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.