releaselisted

Run a versioned release with git-flow discipline: deterministic preflight that reads version state from git (every tag, both branches, their remotes) rather than from the checkout, derives the semver bump from Conventional Commits, writes the changelog entry from fragments, and prints the exact command sequence for THIS repository — consent-gated by default (configurable auto mode). The workflow itself lives in .supermodo/rules/release.md, materialized once from a shipped template (light dev→main, full git-flow with release/* and hotfix/*, or request-based for a protected main). Renders git commands from verified facts and never invents a forge's — publishing is the project's own step, written into its rules file. Use for 'release', 'cut a release', 'ship a version', 'bump the version', 'publish vX.Y.Z', 'hotfix production' — whenever accumulated work should become a tagged, published version.
supermodo/skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill supermodo/skills

# release — versioned releases with git-flow discipline > **Requires:** the sibling `protocols` skill (shared protocol masters); uses `skills.config.json` when present (`release` section — defaults apply without it). Missing protocols → tell the user to install the full supermodo package. The message of this skill: **`main` only ever contains released states** (it is what installers and users consume), so releasing is a deliberate, gated act. Everything scriptable is scripted; git mutations pass a consent gate that defaults to an explicit per-release yes (the yes IS the authorization, for THIS release only) and can be relaxed to auto via `confirmations` in config. > **Cross-tool note (Claude Code ↔ Codex).** Written in Claude Code idioms. > Under Codex: run the same script with `node`, ask the questions in chat, and > execute the same git sequences with your native shell tool. ## Configuration `skills.config.json` → `release` section (all optional, defaults per `../protocols/references/config.md`): `branches.main`/`branches.dev`, `versionFile` + `versionPath` (where the version lives — `package.json:version`, `.claude-plugin/plugin.json:version`, …), `changelog`, `tagPrefix`, `tagStyle`, `mergeStrategy` (`"squash"` default | `"merge"`), `remote`, `versionPattern`, `alphaPolicy`. Nothing in this section names a forge or an integration mode: how the main branch is written and what publishes the release are steps of the process, and they live in the rules file in the projec