releaselisted
Install: claude install-skill zahidakhyar/skills
# Release
Run the version bump + CHANGELOG → push + tags → release PR cycle in one go, then the GitHub release after merge. Final output: the new version + the PR URL.
Arguments: `/release <major|minor|patch>`. No argument → ask for the bump type first (show the current version from the version file so the user can pick easily).
Version file: `package.json`, else `.claude-plugin/plugin.json` (a Claude Code plugin, which has no `package.json`).
## Flow
1. **Check state** — `git status --porcelain` must be clean (`npm version` refuses a dirty tree). Uncommitted changes → stop: ask the user to commit/stash first. Also make sure a version file exists; neither `package.json` nor `.claude-plugin/plugin.json` → stop, this skill has nothing to bump.
Multi-project workspace (e.g. `acme/`, the `workspace/` root): `cd` into the repo that owns the target version file first, not the workspace root.
2. **Detect the repo's branch convention** (never assume, every repo differs):
- Check the project's CLAUDE.md for a release convention (e.g. a `## Loop Config` block with `Release branch`).
- Nothing there: repo has `dev`/`develop` + a default branch (`main`/`master`) → source = dev, PR target = default branch (the dev→main release pattern).
- Repo has only one main branch → source = default branch, but the bump happens on a new branch `release/vx.x.x` (never commit straight to main), PR → default branch.
- Still ambiguous (e.g. many long-lived branches, no clear pattern)