New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release

by heyitsnoah in heyitsnoah/claudesidian

Automatically bump version, update changelog, commit, tag, and push a new release based on recent changes.

MITAuto-check: notesDevelopment

Install Release

skills CLI
$ npx skills add heyitsnoah/claudesidian --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install heyitsnoah/claudesidian release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/heyitsnoah/claudesidian.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release
GitHub stars
2.6k
Token cost
~1.5k tokens
SKILL.md length
613 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Automatically bump version, update changelog, commit, tag, and push a new release based on recent changes.

  • Works in 6 steps: Analyze recent commits since last tag to… → Update version in package.json → Move "Unreleased" entries in… → …
  • The user wants to cut a release
  • SKILL.md covers Task, Process, Version Bump Rules and Example Usage, plus 2 more sections
  • Calls git, claude and gh; reaches github.com

What it does

Release is an agent skill from heyitsnoah/claudesidian. Automatically bump version, update changelog, commit, tag, and push a new release based on recent changes. Use when the user wants to cut a release, publish a new version, bump the version, or run the release workflow.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Git, npm and GitHub. The licence is MIT.

When your agent uses it

  • The user wants to cut a release
  • Publish a new version
  • Bump the version
  • Run the release workflow

Example prompts

  • “/release”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, MultiEdit, Bash, Grep

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Analyze recent commits since last tag to determine version bump type
  2. Update version in package.json
  3. Move "Unreleased" entries in CHANGELOG.md to the new version section
  4. Commit the changes
  5. Create an annotated git tag
  6. Push commits and tags to GitHub

What it can do on your machine

Read from SKILL.md and the folder at commit 6c56f35. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • MultiEdit
    • Bash
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • claude
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release loads about 1.5k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 613 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, MultiEdit, Bash, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from heyitsnoah/claudesidian at commit 6c56f35, republished under its MIT licence (© heyitsnoah). 613 words, ~1,454 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Automatically bump version, update changelog, commit, tag, and push a new release based on recent changes. Use when the user wants to cut a release, publish a new version, bump the version, or run the release workflow.
allowed-tools
Read, Write, Edit, MultiEdit, Bash, Grep

Release Command

Automates the entire release process: analyzes recent commits to determine version bump type, updates version in package.json, moves unreleased changelog entries to the new version, commits everything, creates a git tag, and pushes to GitHub.

Task

  1. Analyze recent commits since last tag to determine version bump type
  2. Update version in package.json
  3. Move "Unreleased" entries in CHANGELOG.md to the new version section
  4. Commit the changes
  5. Create an annotated git tag
  6. Push commits and tags to GitHub

Process

  1. Check Prerequisites

    • Ensure on main/master branch
    • Check for uncommitted changes
    • Verify CHANGELOG.md and package.json exist
    • Get current version from package.json

  2. Determine Version Bump

    • If argument provided (major/minor/patch), use that
    • Otherwise, analyze commits since last tag:
      • Look for "BREAKING CHANGE" or "!" = major bump
      • Look for "feat:" = minor bump
      • Look for "fix:", "docs:", "chore:" = patch bump
    • Calculate new version number

  3. Update Files

    • Update version in package.json
    • Move "Unreleased" section in CHANGELOG.md to new version section
    • Add comparison links for the new version
    • Create new empty "Unreleased" section

  4. Git Operations

    • Stage changes: git add package.json CHANGELOG.md
    • Commit: git commit -m "chore: release v{version}"
    • Create annotated tag: git tag -a v{version} -m "Release v{version}"
    • Push commits: git push
    • Push tags: git push --tags

  5. Create GitHub Release

    • Use gh release create to publish the release automatically
    • Extract the version section from CHANGELOG.md for release notes
    • Include the "Generated with Claude Code" footer
    • This ensures the release is visible in GitHub's releases page

  6. Provide Confirmation

    • Show the GitHub release URL
    • Confirm successful publication

Version Bump Rules

Semantic Versioning (MAJOR.MINOR.PATCH)

Quick Decision Guide:

  • Can users do something they couldn't do before? → MINOR
  • Did something that worked break? → MAJOR (if breaking) or PATCH (if fixing)
  • Did something that worked get better? → PATCH

MAJOR (1.0.0 → 2.0.0):

  • Breaking changes that require users to change their code/config
  • Removing features or commands
  • Changing command syntax or behavior incompatibly
  • Commits with "BREAKING CHANGE" in body
  • Commits with "!" after type (e.g., "feat!:")

MINOR (1.0.0 → 1.1.0):

  • NEW capabilities added (not enhancements to existing features)
  • Making something possible that wasn't possible before
  • New commands, new tools, new integrations
  • New optional features that don't affect existing functionality
  • Significant architectural changes that enable new functionality
  • Commits starting with "feat:" that add NEW functionality
  • Examples:
    • Adding a new /command
    • Adding a new MCP server
    • Adding vault import capability (first time)
    • Making upgrade work without git connection (was impossible before)
    • Enabling a feature to work offline when it required internet before
Show full SKILL.md (202 more words)Show less

PATCH (1.0.0 → 1.0.1):

  • Bug fixes and minor improvements
  • Enhancements to existing features (that already worked)
  • Performance improvements
  • Documentation updates
  • Refactoring without changing behavior
  • Commits with "fix:", "docs:", "style:", "refactor:", "perf:", "test:", "chore:"
  • Examples:
    • Making an existing command smarter (but not enabling new use cases)
    • Improving error messages
    • Fixing bugs in existing features
    • Enhancing existing import to be more intelligent
    • Improving UI/formatting of existing features
Commit Message Best Practices

Use "feat:" only for NEW features:

  • ✅ feat: add vault import capability
  • ❌ feat: enhance vault import (should be fix: or refactor:)

Use "fix:" for improvements and corrections:

  • ✅ fix: improve vault detection accuracy
  • ✅ fix: correct file counting in init-bootstrap

Use "refactor:" for code improvements:

  • ✅ refactor: enhance profile building with URL fetching
  • ✅ refactor: make init-bootstrap questions smarter

Use "perf:" for performance improvements:

  • ✅ perf: optimize vault analysis for large vaults

Example Usage

bash
# Auto-detect version bump from commits
claude run release

# Force specific version bump
claude run release patch
claude run release minor
claude run release major

# Example output:
# 📦 Current version: 0.1.0
# 🔍 Analyzing commits since last release...
#
# Found commits:
# - feat: add video support to Gemini Vision
# - docs: update README with setup instructions
# - fix: correct attachment link handling
#
# ✨ Detected version bump: MINOR (new features added)
# 📝 New version: 0.2.0
#
# ✅ Updated package.json
# ✅ Updated CHANGELOG.md
# ✅ Committed changes
# ✅ Created tag v0.2.0
# ✅ Pushed to GitHub
# ✅ Created GitHub release
#
# 🎉 Release v0.2.0 complete!
#
# GitHub Release: https://github.com/user/repo/releases/tag/v0.2.0

Error Handling

  • If not on main branch: "Please switch to main branch first"
  • If uncommitted changes: "Please commit or stash changes first"
  • If no changes since last release: "No changes to release"
  • If version already exists: "Version X.X.X already exists"

Safety Features

  • Dry run mode: Show what would happen without making changes
  • Confirmation prompt before pushing
  • Validation of version format
  • Check for existing tags before creating

© heyitsnoah, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/release of heyitsnoah/claudesidian.

Open the folder on GitHubat commit 6c56f35

Compare with similar skills

Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillheyitsnoah/claudesidian2.6k—~1.5kAutomated safety check: NotesMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Hunk Release Workflowmodem-dev/hunk9.5k—~3.8kAutomated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
ClawRouter Release ChecklistBlockRunAI/ClawRouter6.6k—~1.4kAutomated safety check: PassMIT
Release Clawpatchopenclaw/clawpatch813—~1.1kAutomated safety check: PassMIT

Similar skills

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Hunk Release Workflow

    modem-dev/hunk

    Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.

    9.5k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • ZCF Release Automation

    UfoMiao/zcf

    Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • ClawRouter Release Checklist

    BlockRunAI/ClawRouter

    Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.

    6.6k GitHub stars~1.4k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Release Clawpatch

    openclaw/clawpatch

    clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.

    813 GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Release

    OvenMediaLabs/OvenPlayer

    Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.

    592 GitHub stars~1.3k tokensUpdated 24 days ago
    DevelopmentAuto-check passed

More from heyitsnoah/claudesidian

All 17 skills in this repo

  • JSON Canvas

    heyitsnoah/claudesidian

    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.

    2.6k GitHub starsUsed in 18 repos~3.5k tokens
    Auto-check passed

  • Add Frontmatter

    heyitsnoah/claudesidian

    Add or update YAML frontmatter properties to enhance Obsidian note organization.

    2.6k GitHub stars~951 tokensUpdated 5 mo ago
    Auto-check passed

  • De AI Ify

    heyitsnoah/claudesidian

    Remove AI-generated jargon and restore human voice to text. An agent skill from heyitsnoah/claudesidian.

    2.6k GitHub stars~526 tokensUpdated 5 mo ago
    Auto-check passed

  • Download Attachment

    heyitsnoah/claudesidian

    Download files from URLs to the Obsidian attachments folder and organize them with descriptive names.

    2.6k GitHub stars~836 tokensUpdated 5 mo ago
    Auto-check passed

  • Git Worktrees

    heyitsnoah/claudesidian

    Work with git worktrees for isolated parallel development. An agent skill from heyitsnoah/claudesidian.

    2.6k GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check: notes

  • Install Claudesidian Command

    heyitsnoah/claudesidian

    Install claudesidian shell command to launch Claude Code from anywhere.

    2.6k GitHub stars~2.7k tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

Automatically bump version, update changelog, commit, tag, and push a new release based on recent changes. Release is an agent skill from heyitsnoah/claudesidian. Automatically bump version, update changelog, commit, tag, and push a new release based on recent changes.

When should I use Release?

Release fits situations like: the user wants to cut a release; publish a new version; bump the version; run the release workflow.

How do I install Release in Claude Code?

Run `npx skills add heyitsnoah/claudesidian --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in heyitsnoah/claudesidian) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add heyitsnoah/claudesidian --skill release -a codex`. Or copy the skill folder (.agents/skills/release in heyitsnoah/claudesidian) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add heyitsnoah/claudesidian --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, claude and gh). Its frontmatter pre-approves these tools: Read, Write, Edit, MultiEdit, Bash, Grep.

Does Release access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Release safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Release use?

Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release?

Skills that share tags, products or a category with Release: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

heyitsnoah (a GitHub user) maintains it in heyitsnoah/claudesidian, which has 2,597 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on April 11, 2026.

Source: heyitsnoah/claudesidian on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.