Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

Release Skills

A universal release workflow that auto-detects your version file, bumps semver, writes multi-language changelogs, and publishes tags plus GitHub Releases.

Dev & CodingIntermediate★ 24,749⑂ 2,764AI score 8/10Last updated: Jul 4, 2026

What it does

  • Auto-detects the version file: package.json, pyproject.toml, Cargo.toml, marketplace.json, or plain VERSION/version.txt.
  • Analyzes commits since the last tag using conventional-commit types, flags breaking changes, and recommends a major/minor/patch bump.
  • Detects changelog language from filename suffixes (CHANGELOG.zh.md, CHANGELOG.ja.md, ...) and writes each changelog natively in that language, with built-in section-title translations.
  • Identifies external PR authors and appends (by @username) attribution.
  • Groups changes per skill/module, creates separate conventional commits, a release commit, and an annotated tag built from an extracted release-notes file.
  • Pushes and creates/updates a GitHub Release via gh, and can backfill missing releases for historical tags with --backfill-releases.
  • Supports an optional .releaserc.yml with prepare_artifact / publish_artifact hooks and placeholder substitution.

Who it's for

  • Open-source maintainers who ship changelogs in several languages and hate writing them by hand.
  • Developers juggling Node.js, Python, and Rust repos who want one consistent release ritual.
  • Monorepo / plugin-marketplace projects that need per-module commits before a release.
  • Anyone cleaning up a repo full of tags with empty GitHub Releases.

Examples

  1. Safe preview: run /release-skills --dry-run to see the detected version file, the proposed bump (1.2.3 → 1.3.0), English and Chinese changelog previews, and the exact commits it would create — with no writes.
  2. Full release: run /release-skills; it splits commits per module, updates the version file, generates all changelogs, commits chore: release v1.3.0, creates the annotated v1.3.0 tag, then pushes and publishes the GitHub Release after your confirmation.
  3. Backfill history: run /release-skills --backfill-releases to find tags without a GitHub Release and create them using the matching changelog section as release notes.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .claude/skills/release-skills folder from the GitHub repo JimLiu/baoyu-skills into my ~/.claude/skills/release-skills/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/JimLiu/baoyu-skills.git /tmp/baoyu-skills && mkdir -p ~/.claude/skills && cp -r /tmp/baoyu-skills/.claude/skills/release-skills ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and go to a working directory of your choice.
  2. Clone the repository: git clone https://github.com/JimLiu/baoyu-skills.git
  3. Create the skills folder if needed: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r baoyu-skills/.claude/skills/release-skills ~/.claude/skills/
  5. Verify it exists: ls ~/.claude/skills/release-skills/SKILL.md
  6. For GitHub Release support, install GitHub CLI and authenticate: gh auth login
  7. Restart Claude Code, open the repository you want to release, and run /release-skills --dry-run first.
  8. If the preview looks right, re-run without --dry-run and answer the confirmation prompts (version bump, push or local-only, publish GitHub Release).
View source on GitHub ↗License: MIT