Skip to main content
skill CX Codex

release · corezoid — Claude Code and Codex skill: automated plugin releases

A skill that walks through six release phases: compares your code to the last tag, suggests a version number, updates seven manifest files, and creates a git tag.

MIT ★ 74 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add corezoid/corezoid-ai-plugin --skill release -a claude-code
Open on GitHub

What release does

Publishing a new version of this plugin touches seven separate manifest files—for Claude Code, Codex, Kiro, the root agent-plugins manifest, two marketplace entries, and POWER.md frontmatter. Missing even one causes inconsistency: platforms request different versions, or the marketplace shows stale data. This skill automates the whole process across all seven files at once.

The skill breaks the release into six sequential phases, asking for approval at each step. It inspects what changed since the last tag and summarizes it, lets you pick a new version number (patch, minor, or major), drafts a CHANGELOG.md entry in the existing style, syncs the version across all seven manifests, shows the complete changeset for review, then commits and tags. After each file edit, it verifies that all seven manifests contain the same version number—if any file lags behind, the skill stops and you fix it before moving on.

This guard prevents releases where CI fails the version-sync check after you've already pushed, or where one platform installs an older build than another. The skill uses RELEASE_CHECKLIST.md as its source of truth; if a new manifest file gets added to the repo, the checklist updates and the skill stays in sync.

What it helps with

  • bump version across seven manifest files without inconsistency
  • write a CHANGELOG entry that matches existing style and tone
  • create and push a release tag after verifying all files
  • summarize what changed since the last release
  • choose the right semantic version bump based on the changes

Example prompts for the agent

  • Release version 2.5.0
  • Cut a new release of the plugin
  • Release with a minor version bump

How to install release

1Skills CLI (Vercel)

npx skills add corezoid/corezoid-ai-plugin --skill release -a claude-code

2Manually: put the files in place

~/.claude/skills/release/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about release

How do I install release in Claude Code?

Run npx skills add corezoid/corezoid-ai-plugin --skill release -a claude-code. The skill will then be available at ~/.claude/skills/release/SKILL.md.

What does release do?

It automates all six steps: reviews what changed since the last tag, lets you pick a version number, drafts a CHANGELOG entry, updates all seven manifest files, displays the full changeset for approval, then commits and tags.

Why use a dedicated skill instead of manual steps?

A release touches seven manifests simultaneously. Forgetting even one causes platforms to disagree on the version or the marketplace to show outdated data. The skill enforces that all seven files stay in sync and verifies them before proceeding.

Source text

SKILL.md · MIT
---
name: release
description: Project release helper for corezoid-ai-plugin. Prepares a new tagged release end-to-end. Use whenever the user says "release", "релиз", "новый релиз", "сделай релиз", "выпусти версию", "bump version", "обновить версию", "tag a release", "/release", or anything that implies cutting a new version of this plugin. Walks through six explicit phases — compare `main` with the latest tag, ask which new version to publish, draft a CHANGELOG.md entry, sync that version across all seven release files, show the full proposed change set for confirmation, then commit and tag — see "The six phases" below for what each does. Always use this skill instead of running release steps manually — it keeps the seven release files in lock-step, formats the changelog consistently, and prevents partial releases.
---

# Release skill

This skill prepares a new tagged release of `corezoid-ai-plugin`. It runs through six phases in order. Do not skip phases, and do not collapse them — the user expects to see and approve each one before the next begins.

## Why a dedicated skill

A release of this plugin touches seven separate manifest files (Claude, Codex, Kiro plugin manifests; the agent-plugins root `plugin.json`; two marketplace manifests; and `POWER.md` frontmatter) plus the changelog. Forgetting any one of them ships a broken or inconsistent release: marketplace listings disagree about the version, Codex/Kiro install the wrong build, or `POWER.md` — which is attached to the GitHub Release artifact set — advertises a stale version. The single source of release truth for this repo is `RELEASE_CHECKLIST.md` — this skill executes that checklist programmatically so nothing is missed.

## The six phases

### Phase 1 — Inspect what changed since the last tag

Goal: understand and summarise everything that has landed since the previous release.

Run, in parallel:

```bash
git fetch --tags --quiet
git describe --tags --abbrev=0                         # the last released tag, e.g. v2.3.9
git log <last-tag>..HEAD --pretty=format:'%h %s'       # commit subjects since that tag
git diff --stat <last-tag>..HEAD                       # files touched, magnitude of change
git status --short                                     # uncommitted work that may need to ship in this release
```

Then read the actual diff for any commit subjects that are vague or for any non-trivial file changes — commit subjects alone often understate what shipped. Pay particular attention to:

- New skills under `plugins/corezoid/skills/` (added directories).
- MCP server changes in `plugins/corezoid/mcp-server/` (new tools, schema changes, breaking behaviour).
- Docs changes in `plugins/corezoid/docs/` and root-level docs (`README.md`, `SECURITY.md`, `CLAUDE.md`).
- CI / workflow changes in `.github/`.

If `git status` shows uncommitted changes, ask the user whether those should be part of this release or stay out of it. Don't assume — pending edits are sometimes the whole point of the release and sometimes unrelated work.

Output to the user: a short bulleted summary grouped by category, the kind of bullets that would end up in the changelog. Use the same vocabulary the existing CHANGELOG.md uses: `Feat:`, `Fix:`, `Docs:`, `Chore:`, `CI:`, `Security:`, `Refactor:`. Keep each bullet to one line.

### Phase 2 — Ask which new version to publish

Goal: get the new semantic version from the user.

Use `AskUserQuestion` with the **current** version pulled from `plugins/corezoid/.claude-plugin/plugin.json` and three suggested bumps:

- Patch (`X.Y.Z+1`) — bug fixes, docs, internal cleanup only.
- Minor (`X.Y+1.0`) — new skills, new MCP tools, additive features.
- Major (`X+1.0.0`) — breaking changes to manifests, MCP tool schemas, or skill contracts.

Recommend a level based on Phase 1 (e.g. if a new skill directory appeared, suggest a minor bump). Always allow the user to override with a custom version via the "Other" answer.

The version the user picks is the only version that should appear anywhere downstream in this skill run. Store it once and reuse it — do not re-derive it.

### Phase 3 — Draft the CHANGELOG.md entry

Goal: produce a new section at the top of `CHANGELOG.md`, matching the existing format exactly.

Read `CHANGELOG.md`. The format is rigid:

```
## [X.Y.Z]

- Feat: …
- Fix: …
- Docs: …
```

Rules:

- The new section goes immediately after the top-level `# Changelog` heading, **before** the previous version.
- Use the same category prefixes seen in prior entries. Don't invent new ones unless the change genuinely doesn't fit (e.g. `Refactor:` is fine, `Stuff:` is not).
- One bullet per logical change, not one bullet per commit. Squash related commits.
- Write in the past tense, imperative-ish style matching prior entries ("add", "fix", "remove" — not "added", "fixes").
- Drop trivia: bumps of internal version numbers, merge commits, formatting-only changes. The changelog is for users of the plugin, not for git archeologists.

Show the drafted entry to the user before writing it to disk. They will often want to reword a bullet or merge two of them — that's expected.

### Phase 4 — Sync the version across all seven release files

Goal: the new version appears in exactly seven places, all in agreement.

The files and the field to update:

| File | Field to edit |
| --- | --- |
| `plugins/corezoid/.claude-plugin/plugin.json` | top-level `"version"` |
| `plugins/corezoid/.codex-plugin/plugin.json` | top-level `"version"` |
| `plugins/corezoid/.kiro-plugin/plugin.json` | top-level `"version"` |
| `plugin.json` (repo root, agent-plugins manifest) | top-level `"version"` |
| `.claude-plugin/marketplace.json` | `plugins[0].version` |
| `.agents/plugins/marketplace.json` | `plugins[0].version` |
| `POWER.md` | YAML frontmatter `version:` |

Use the `Edit` tool with `old_string` containing the full `"version": "..."` (or `version: ...` for `POWER.md`) line so the replacement is unambiguous. Do not rewrite the whole file. Do not touch any other field — license, description, paths must stay as-is.

After editing, verify with a single grep:

```bash
grep -nE '"version"|^version:' \
  plugins/corezoid/.claude-plugin/plugin.json \
  plugins/corezoid/.codex-plugin/plugin.json \
  plugins/corezoid/.kiro-plugin/plugin.json \
  plugin.json \
  .claude-plugin/marketplace.json \
  .agents/plugins/marketplace.json \
  POWER.md
```

All seven lines must show the new version. If any one disagrees, fix it before moving on — never proceed to commit with mismatched manifests. CI's `Version sync across manifests` step and the release workflow's `guard` job both enforce this; a stale file will fail the release before any binary is built. That step in `.github/workflows/ci.yml` is the authoritative list: if it names a file this table lacks, bump that file too and add it here. v3.11.0 was first tagged with the root `plugin.json` still on the old version because this table listed six files.

Then validate that the JSON still parses:

```bash
python3 -m json.tool .claude-plugin/marketplace.json >/dev/null
python3 -m json.tool .agents/plugins/marketplace.json >/dev/null
python3 -m json.tool plugins/corezoid/.claude-plugin/plugin.json >/dev/null
python3 -m json.tool plugins/corezoid/.codex-plugin/plugin.json >/dev/null
python3 -m json.tool plugins/corezoid/.kiro-plugin/plugin.json >/dev/null
python3 -m json.tool plugin.json >/dev/null
```

### Phase 5 — Confirm with the user

Goal: nothing is committed without explicit go-ahead.

Show the user:

1. The new version number.
2. The CHANGELOG.md entry as it will be written.
3. A `git diff --stat` of all currently staged/unstaged changes (including any pre-existing edits from Phase 1 that they confirmed should ship).
4. The exact commit message and tag name you intend to create.

Then use `AskUserQuestion` with options like "Proceed with commit and tag" / "Let me edit something first". Do not proceed without an affirmative answer. If the user wants to tweak the changelog or change the version, loop back to the relevant phase rather than improvising in place.

### Phase 6 — Commit and tag

Goal: a single release commit plus a matching annotated git tag on the current branch.

Stage only the files this skill touched plus any files the user confirmed should ship:

```bash
git add CHANGELOG.md \
        plugins/corezoid/.claude-plugin/plugin.json \
        plugins/corezoid/.codex-plugin/plugin.json \
        plugins/corezoid/.kiro-plugin/plugin.json \
        plugin.json \
        .claude-plugin/marketplace.json \
        .agents/plugins/marketplace.json \
        POWER.md
# Plus any other files the user explicitly approved in Phase 1.
```

Avoid `git add -A` / `git add .` — there may be unrelated untracked files (samples, local docs, IDE state) that must not enter the release commit.

Commit message format (matches recent release commits in this repo):

```
chore(release): vX.Y.Z

- Brief one-line summary of the biggest change.
- Optional second bullet if there's another standout.
```

Use a HEREDOC for the commit so multiline formatting is preserved. Do not add Claude co-author trailers to release commits — these are public and authored by the maintainer.

Then create the tag:

```bash
git tag -a vX.Y.Z -m "Release vX.Y.Z"
```

Use the **annotated** form (`-a`) so `git describe` and GitHub Releases pick it up correctly. The unannotated `git tag vX.Y.Z` form will work but is inferior.

Do **not** push automatically. After the commit and tag are created, tell the user exactly what to run to push:

```bash
git push origin <current-branch>
git push origin vX.Y.Z
```

This deliberate pause is a safety net — pushing the tag triggers `release.yml` and a public GitHub Release, which is hard to undo. Let the user do that last step themselves.

## Things to watch for

- **Wrong branch.** Releases typically come from `main`. If the current branch is something else (e.g. `develop`), surface this in Phase 5 so the user can decide whether to merge first or release from where they are.
- **Tag already exists.** Before Phase 6, run `git tag -l vX.Y.Z`. If it returns the tag, stop — the version is already taken. Ask the user to pick a different one and loop back to Phase 2.
- **Unrelated untracked files.** The repo often has work-in-progress files (`comparison.html`, `plan.html`, sample `.conv.json` files, IDE config). These must not enter the release commit unless the user explicitly says they should.
- **Manifest drift in the diff.** If Phase 1 shows a manifest file already changed by a previous (incomplete) attempt, treat that as suspect — re-read all seven release files before Phase 4 and reconcile from a known state, don't blindly bump on top of a half-finished bump.
- **CHANGELOG.md already has an entry for the chosen version.** That means a previous release attempt was partially completed. Show the existing entry to the user and ask whether to extend it, replace it, or pick a different version.

## When the user wants a one-shot, no-questions release

If the user explicitly says something like "just release a patch, no questions" or "автоматический релиз патча", you can fold Phase 2 (pick patch bump) and Phase 5 (confirmation) into a single approval at the end, but never skip showing the proposed changelog entry and the proposed version. The seven-file sync is non-negotiable regardless of speed mode.

© corezoid · MIT · corezoid/corezoid-ai-plugin

Similar skills

All skills for Agent setup: memory, context, orchestration →

release by other authors comes first.

release tobi A skill for Claude Code, Codex, Cursor and other IDE agents that manages project releases: validates CHANGELOG.md, updates dependencies, installs git hooks and cuts releases on command. Runs with /release 1.0.5 or /release patch. CX Codex +1 2,200installs release Yeachan-Heo A repo-aware skill that discovers release rules from CI files, caches them in .omc/RELEASE_RULE.md, and guides releases. Helpful when preparing tags and version bumps. CX Codex +1 904installs Release schpet Release is a Claude Code skill that reviews changes, updates the changelog, and publishes a version. It activates for requests to prepare or create a release. CX Codex +1 3,900installs release different-ai Cuts an OpenWork release from a git tag through GitHub Actions, with no commits to the repo. Checks open fix PRs before tagging and covers reruns after a failure. CX Codex +1 122installs release toss Automates project releases by verifying git status, bumping versions in package files, generating changelog entries, and tagging commits. CX Codex +1 208installs prepare-release mysticaltech prepare-release prepares releases in the terraform-hcloud-kube-hetzner repo: changelog, version bumps, release notes draft. Pushes no tag unless the maintainer says so. CX Codex +1 1installs jackin-release jackin-project jackin-release orchestrates checks, changelog formatting, and version bumps for Rust projects. Runs cargo release only after an explicit confirmation from the operator. CX Codex +1 469installs auto-release-manager Dev-GOM auto-release-manager bumps the version in your project files, builds a CHANGELOG from commits and carries the release through tag and push. Handy when the same release ritual repeats in every repo. CX Codex +1 3installs cmux-release manaflow-ai Automates the cmux release pipeline by extracting changelog lines from pull requests, bumping versions, and running safety checks. CX Codex +1 5,000installs github-release-management ruvnet github-release-management is a Claude Code skill that coordinates GitHub release work. It engages with requests involving versioning, tests, deployment, and rollback. CX Codex +1 1,200installs w-release blockmatic-icebox w-release is a Claude Code skill that reviews release impact, changelog changes, and template contracts. Invoke it manually; automatic invocation is disabled. CX Codex +1 647installs

From the same set30

The whole set →
corezoid-node-layout corezoid-node-layout arranges Corezoid process nodes into a readable top-to-bottom flow and moves error handling to the right. Use it before pushing a new process or after a layout request. CX Codex +1 ★ 74repo stars corezoid-access corezoid-access — a skill for managing access to processes, folders and projects in Corezoid. Share objects with users and groups, create API keys, invite external users, and audit who has access. CX Codex +1 ★ 74repo stars corezoid-project-review corezoid-project-review audits entire Corezoid projects or folders, finding circular calls, duplicate code logic, and shared hardcoded secrets. CX Codex +1 ★ 74repo stars corezoid-init corezoid-init connects a working directory to Corezoid, handles sign-in, and pulls a selected stage. Use it when starting a Corezoid project. CX Codex +1 ★ 74repo stars corezoid-state-diagram-create corezoid-state-diagram-create designs Corezoid state diagrams with conv_type: state, sets up entity lifecycles, and generates valid diagram JSON files. CX Codex +1 ★ 74repo stars corezoid-process-optimizer corezoid-process-optimizer reviews Corezoid process JSON and proposes or applies changes such as merging nodes, cleaning data, and filling missing titles. CX Codex +1 ★ 74repo stars corezoid-connector-create corezoid-connector-create — a skill that generates a Corezoid process calling a single endpoint of any HTTP API (Stripe, OpenWeather, banks, CRM, or your own service). CX Codex +1 ★ 74repo stars corezoid-gitcall corezoid-gitcall configures isolated Git Call nodes in Corezoid processes to execute custom code in 9 languages or Docker when native nodes are insufficient. CX Codex +1 ★ 74repo stars

Project sponsors

Companies that keep this analytics open