How do I install the Release Assistant skill?

Run npx skillmds@latest add fubira/release-assistant in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Assistant safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Assistant?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Assistant free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Assistant?

fubira (@fubira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Assistant by fubira — Agent Skill

Name: Release Assistant
Rating: 4.666666666666667 (3 reviews)
Author: fubira

Release Assistant

Runs the release workflow for Node/Bun and Go projects — version bump from commit history, mandatory lint/build/test, then tag creation and push. Use when the user asks to release, cut a version, or publish a tag. Do not use for ordinary commits or for merging to main.

fubira Updated Sep 10, 2026

File contents

Release Assistant Skill

Automate release workflows: Lint → Build → Test → Version Bump → Tag → Push.

Activation Triggers

"release", "version bump"
/patch-release → Patch Release flow

Project Type Detection

Indicator	Project type	Version source	Bump method
`package.json` present	Node/Bun	`package.json`	Edit file + tag
`go.mod` only (no package.json)	Go	git tag	Tag only (no file edit)
`Cargo.toml`	Rust	`Cargo.toml`	Edit file + tag
Other	Unknown	Ask user	Abort and confirm

Git tag format is vX.Y.Z for all types.

Workflow

Phase 1: Pre-flight Checks

Do NOT proceed until ALL checks pass.

git status — abort if uncommitted changes
Run project's lint / build / test commands (check package.json scripts, Makefile, or standard defaults like go build ./... / go test ./...)
- lint failure: try auto-fix (--write etc.), abort if not fixable
- build failure: abort
- test failure: abort (skip phase if no test target defined)

Phase 2: Version Analysis

Determine current version:
- Node: package.json + latest v* tag
- Go: latest v* tag only
Analyze commits: git log <last-tag>..HEAD --oneline
Determine bump type (Conventional Commits):
- MAJOR: BREAKING CHANGE or type!: present
- MINOR: feat: present (no breaking)
- PATCH: only fix/refactor/docs/chore
Group commits by type, present summary to user

Phase 3: Version Bump & Commit

Propose new version, get user confirmation (override allowed)
Node/Rust: Edit manifest file. Go: skip file edit
Commit (Node/Rust only) with subject chore(release): Bump version to X.Y.Z (format and trailer per git-commit-assistant), then git tag vX.Y.Z

Phase 4: Push

Confirm push with user (show branch name and tag)
git push origin <branch> && git push origin vX.Y.Z
Show release summary, prompt to check CI/CD pipeline

Patch Release (`/patch-release`)

Simplified flow for bug-fix-only releases (no feat commits).

Skip version analysis (always PATCH)
Tests optional (build includes type checking for Node)
Skip changelog, minimize confirmation steps

Error Handling

Error	Action
Lint failure	Auto-fix with `--write` → abort if not fixable
Test/Build failure	Abort, prompt to fix
Uncommitted changes	Suggest commit/stash, abort
Tag already exists	Abort, suggest delete or different version
Push failure	Suggest solution based on error message

---name: release-assistantdescription: Runs the release workflow for Node/Bun and Go projects — version bump from commit history, mandatory lint/build/test, then tag creation and push. Use when the user asks to release, cut a version, or publish a tag. Do not use for ordinary commits or for merging to main.---# Release Assistant SkillAutomate release workflows: Lint → Build → Test → Version Bump → Tag → Push.## Activation Triggers- "release", "version bump"- `/patch-release` → Patch Release flow## Project Type Detection| Indicator | Project type | Version source | Bump method ||-----------|-------------|---------------|-------------|| `package.json` present | Node/Bun | `package.json` | Edit file + tag || `go.mod` only (no package.json) | Go | git tag | Tag only (no file edit) || `Cargo.toml` | Rust | `Cargo.toml` | Edit file + tag || Other | Unknown | Ask user | Abort and confirm |Git tag format is `vX.Y.Z` for all types.## Workflow### Phase 1: Pre-flight Checks**Do NOT proceed until ALL checks pass.**1. `git status` — abort if uncommitted changes2. Run project's lint / build / test commands (check `package.json` scripts, `Makefile`, or standard defaults like `go build ./...` / `go test ./...`) - **lint** failure: try auto-fix (`--write` etc.), abort if not fixable - **build** failure: abort - **test** failure: abort (skip phase if no test target defined)### Phase 2: Version Analysis1. Determine current version: - Node: `package.json` + latest `v*` tag - Go: latest `v*` tag only2. Analyze commits: `git log <last-tag>..HEAD --oneline`3. Determine bump type (Conventional Commits): - **MAJOR**: `BREAKING CHANGE` or `type!:` present - **MINOR**: `feat:` present (no breaking) - **PATCH**: only `fix`/`refactor`/`docs`/`chore`4. Group commits by type, present summary to user### Phase 3: Version Bump & Commit1. Propose new version, get user confirmation (override allowed)2. Node/Rust: Edit manifest file. Go: skip file edit3. Commit (Node/Rust only) with subject `chore(release): Bump version to X.Y.Z` (format and trailer per git-commit-assistant), then `git tag vX.Y.Z`### Phase 4: Push1. Confirm push with user (show branch name and tag)2. `git push origin <branch> && git push origin vX.Y.Z`3. Show release summary, prompt to check CI/CD pipeline## Patch Release (`/patch-release`)Simplified flow for bug-fix-only releases (no `feat` commits).- Skip version analysis (always PATCH)- Tests optional (build includes type checking for Node)- Skip changelog, minimize confirmation steps## Error Handling| Error | Action ||-------|--------|| Lint failure | Auto-fix with `--write` → abort if not fixable || Test/Build failure | Abort, prompt to fix || Uncommitted changes | Suggest commit/stash, abort || Tag already exists | Abort, suggest delete or different version || Push failure | Suggest solution based on error message |

Frequently asked questions