release

release is a skill for Claude Code from heyitsnoah/claudesidian. It costs 49 tokens per session (1,429 once invoked), scanned A, original, MIT.

A release procedure that determines a version change, updates the package version and changelog, then commits, tags, and pushes the result to GitHub.

In plain words
What is it for?
Checking the branch and working tree, choosing major, minor, or patch changes from commits or an argument, updating release files, creating annotated tags, and pushing commits and tags.
Why use it?
It groups the repetitive release steps and checks repository conditions before publishing a new version.

Skill for Claude Code

About the project

Claudesidian is a preconfigured Obsidian vault structure that lets Claude Code help manage a personal knowledge base as a thinking partner. It is for people who organize notes and other knowledge in Obsidian, with Git-based version control and optional integrations for image analysis and web research. The catalogue add-ons provide Claude Code skills, agents, hooks, and settings for working with this vault.

heyitsnoah/claudesidian · 2,582 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/heyitsnoah/claudesidian/release
Any agent
npx skills add heyitsnoah/claudesidian --skill release
Clone the repo
git clone --depth 1 https://github.com/heyitsnoah/claudesidian

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/heyitsnoah/claudesidian/release.svg)](https://agentmods.dev/skills/heyitsnoah/claudesidian/release)
Your own site
<a href="https://agentmods.dev/skills/heyitsnoah/claudesidian/release"><img src="https://agentmods.dev/badge/skills/heyitsnoah/claudesidian/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,429 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01429
Opus 5 $0.00024 $0.00714
Sonnet 5 $0.00010 $0.00286
Haiku 4.5 $0.00005 $0.00143

Measured 6d ago against content hash 464ff3faed18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/release/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

Read the full file on GitHub · 181 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 181 lines · 49 tokens per session scan A 464ff3faed18

Subscribe to this mod's changes

release is a skill published in the GitHub repository heyitsnoah/claudesidian (2,582 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.