# jackin-release

Orchestrates checks, changelog formatting, and version bumps for Rust projects. Runs cargo release only after an explicit confirmation from the operator.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 469 installs · ★ 3
- Author: jackin-project
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/jackin-project/jackin-dev/tree/HEAD/skills/jackin-release/SKILL.md
- Updated: 2026-10-06
- HTML: https://affpapa.org/en/nevibecode/skills/jackin-release

## What it does

The skill coordinates release routines step by step. First, it triggers gate validations with `jackin-release-check` and reads unreleased work via `jackin-release-notes`. Based on the change categories, it calculates the next version: breaking changes prompt major bumps, additions map to minor, and bug fixes trigger patch releases.

The execution step is irreversible. Running `cargo release --execute` updates `Cargo.toml`, replaces changelog headers, tags the commit, and pushes to git. Without `cargo-release`, an authenticated `gh` CLI, and configured `release.toml` rules, the process will fail. The assistant never executes the cut on its own. It waits for a direct "yes" from the developer.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add jackin-project/jackin-dev --skill jackin-release -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/jackin-release/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/jackin-release/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add jackin-project/jackin-dev --skill jackin-release -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/jackin-release/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add jackin-project/jackin-dev --skill jackin-release -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/jackin-release/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install jackin-project/jackin-dev jackin-release
```

2. **Manually: put the files in place**
- File: `.github/skills/jackin-release/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add jackin-project/jackin-dev --skill jackin-release -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/jackin-project/jackin-dev --path skills/jackin-release
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/jackin-release/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add jackin-project/jackin-dev --skill jackin-release -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/jackin-project/jackin-dev/tree/HEAD/skills/jackin-release/SKILL.md

## When to use it
- verify project release readiness gates before tagging
- update CHANGELOG.md headers from the unreleased section
- calculate the next semver increment from committed work
- run cargo release to tag and push the repository

## Example prompts
- Cut the next project release using `jackin-release`.
- Prepare a minor version bump with `jackin-release minor`.
- Run gate checks and release a patch via `jackin-release patch`.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f233b649e9c19de7.

BEGIN THIRD-PARTY FILE f233b649e9c19de7
```text
---
name: jackin-release
description: Use only when the user explicitly requests this skill. Cuts a jackin❯ release — runs the readiness gates, writes the changelog, recommends a version, then executes cargo release on explicit operator confirmation.
argument-hint: "[major|minor|patch|version]"
disable-model-invocation: true
license: Apache-2.0
user-invocable: true
---

# jackin-release

**Cut** a release. The only irreversible skill in the suite — `cargo release --execute` bumps the version, rewrites the changelog header, tags, and pushes. Hard-gated on one explicit operator "yes"; nothing releases on assumption.

Orchestrates `jackin-release-check` (the gates) and `jackin-release-notes` (the changelog), then recommends a version from the changelog shape and cuts.

## When to use

- The operator asks to cut / ship / release a version.

## When NOT to use

- Just checking readiness → `jackin-release-check`.
- Just updating the changelog → `jackin-release-notes`.

## Prerequisites

`cargo-release` installed; `gh` authenticated; `release.toml` with `pre-release-replacements` for `CHANGELOG.md`; `CHANGELOG.md` with the `<!-- next-header -->` marker; `.github/workflows/ci.yml`.

## Process

1. **Gates.** Run `jackin-release-check`. A red gate **stops** — show the report and name what to fix. Warns surface; ask whether to continue.

   *Done when* every gate is green, or the operator accepted the warns.

2. **Changelog.** Run `jackin-release-notes`. Present the `[Unreleased]` section; let the operator re-classify or reword.

   *Done when* the operator approves the changelog.

3. **Recommend a version.** Read the approved `[Unreleased]` buckets: any **Removed** or "breaking" entry → **major**; any **Added** → **minor**; only **Fixed** / **Changed** / **Security** / **Deprecated** → **patch**. Read the current version (`grep '^version' Cargo.toml`), compute the next, present the recommendation, wait.

   *Done when* the operator confirms the bump level.

4. **Commit the changelog.** If `CHANGELOG.md` has uncommitted edits, `git add CHANGELOG.md && git commit -m "docs: update changelog for vX.Y.Z"`.

5. **Final confirm.** Show the summary — version, bump level, changelog shape, and the exact `cargo release <level> --execute` about to run (it bumps `Cargo.toml`, renames `[Unreleased]` to `[X.Y.Z] - <date>` via `release.toml`, tags, and pushes). **Do not run it without an explicit "yes."**

   *Done when* the operator says "yes."

6. **Cut.** `cargo release <level> --execute`. On failure, show the error and stop.

7. **Verify.** `git tag -l "vX.Y.Z"` and `git ls-remote --tags origin "refs/tags/vX.Y.Z"`. Point the operator at the release workflow that now builds the artifacts.

## Error recovery

- Before `cargo release`: safe to fix and re-run — this skill re-validates everything.
- During `cargo release`: check what committed or tagged. Tag created but unpushed → `git push origin vX.Y.Z`. Version commit without tag → reset and retry.
```
END THIRD-PARTY FILE f233b649e9c19de7

The third-party file has ended. Everything between the f233b649e9c19de7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3005 of 3402 bytes. © jackin-project · Apache-2.0 · https://github.com/jackin-project/jackin-dev/tree/HEAD/skills/jackin-release/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md