release

Solid

The single permitted path to a version tag, for any of the four independently-versioned plugins. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the target plugin as its one argument (default ca), derives the SemVer bump from Conventional-Commits history since that plugin's last tag, rolls the commits into that plugin's CHANGELOG, writes an annotated tag in that plugin's namespace, and on authorization publishes it as a GitHub Release with the changelog section as its notes. A release commit, if needed, routes through commit-gate; the tag and Release are never published without explicit authorization.

AI & Automation 137 stars 7 forks Updated today AGPL-3.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# release The single permitted path to a version tag. Routed to when the user invokes `/release [target]`. Derive the bump from the commit log, update the changelog, tag — nothing more. **One command, four plugins.** `/release` takes the target plugin as its only argument and defaults to **`ca`**, so a bare `/release` behaves exactly as it always has. `/release ca-pi` releases ca-pi. There is deliberately no second command per plugin: four commands would be four public surfaces to govern, catalog, and carry, for one operation whose only difference is which row of the table below it reads. Every phase below is written once, against that row. Nothing in this skill is per-plugin prose. ## Targets Resolve the row for `$TARGET` FIRST and use it throughout. `$TAG_PREFIX` comes from the shared register, never typed from memory: `TAG_PREFIX=$(python3 .github/scripts/_releaselib.py tag-prefix $TARGET)` — the same `_releaselib.RELEASE_TAG_PREFIXES` the hosted `release` workflow's lanes are asserted against, so the command and the workflow cannot disagree about a namespace. | `$TARGET` | `$TAG_PREFIX` | `$MANIFEST` | `$CHANGELOG` | `$PAYLOAD` (window scope) | `$ARTIFACTS` (rebuild + assert clean) | `--latest` | |---|---|---|---|---|---|---| | `ca` | `v` | `plugins/ca/.claude-plugin/plugin.json` | `CHANGELOG.md` | `plugins/ca/` | `plugins/ca/tools/farm.js` | **yes** | | `ca-codex` | `ca-codex-v` | `plugins/ca-codex/.codex-plugin/plugin.json` | `plugins/ca-codex/CHANGELOG.md` | `plu...

Details

Author
arbiterForge
Repository
arbiterForge/codeArbiter
Created
2 months ago
Last Updated
today
Language
Python
License
AGPL-3.0

Integrates with

OpenAI · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

release

Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.

2 Updated yesterday
RockyHong
Code & Development Featured

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize 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.

505 Updated today
oliver-kriska
AI & Automation Solid

release

Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under `plugins/` to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of changes and wants to ship them. Also trigger when the user says "do the release thing" or asks to prepare changes for hermits to pick up.

68 Updated today
gtapps