agentleFS
Sign inStart free
Edmonds-Commerce-LimitedEdmonds-Commerce-Limited/claude-code-hooks-daemon/.claude/skills/release/SKILL.md

release

Skill4 starsChanged 16 days agoMITView on GitHub

Automated release management - version updates, changelog generation, git tagging, and GitHub release creation

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not START a release because a cron tick fired, because a plan says "finish the release", or because the tree looks ready.

    line 30
  2. Distinctive:

    Follow its output exactly.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 186 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/release - Automated Release Management Skill

🚨 HUMAN-GATED — this skill is the ONLY valid entry point

A release may only begin when a human invokes /release in the CURRENT session. An agent must never start a release on its own initiative. The /release invocation is the ONLY authorisation there is: once the pipeline's blocking gates pass, the release proceeds through merge, tag and publish with no secondary human confirmation — it passes, or a failed gate aborts it.

A release is a decision about scope, which only the human can see. The rule, the state file (untracked/release-state.json, written once Stage 0's slate-clean gate returns 0, never before), the resume rules and how to recover from an unauthorised release are all in RELEASING.md — "A RELEASE IS HUMAN-GATED".

  • No state file ⇒ no release in progress. A dirty tree, an open release/* branch or a plan saying "finish the release" is not a substitute — ask.
  • State file present ⇒ resume from last_completed_step and carry the release through to Step 15.

Do not START a release because a cron tick fired, because a plan says "finish the release", or because the tree looks ready.

Run this first

Claude Code loads this markdown and nothing else — the file below is not run for you, and it holds the procedure to follow (Plan 00324):

bash "${CLAUDE_SKILL_DIR:-.claude/skills/release}/invoke.sh" <major|minor|patch|X.Y.Z> [accept-wip]

Follow its output exactly; what is written here is orientation.

Usage

/release                 # auto-detect version bump from commits
/release 2.2.0           # explicit version
/release patch           # bump type: major | minor | patch
/release 2.2.0 accept-wip  # proceed over in-flight work the slate gate reported

What It Does

Executes the pipeline in RELEASING.md "Pipeline Overview" — the single source of truth for the steps, their order, their numbering and which are BLOCKING gates. In outline only: prepare on a release/<version> branch, open a pull request whose CI runs the whole QA gate, then — in this session, with the daemon live — run the acceptance tests, merge the pull request, tag the merge commit and publish. While the pull request is open, other merges to main are frozen (R-RELEASE-MERGE-FREEZE).

This skill does not restate any step; a step number anywhere in this file is RELEASING.md's numbering. Any blocking-gate failure ABORTS the release.

Agent

The release agent (.claude/agents/release-agent.md) prepares the release files (RELEASING.md Steps 1b–5). Main Claude orchestrates every other step; agents cannot spawn nested agents.

Documentation

📖 SINGLE SOURCE OF TRUTH: CLAUDE/development/RELEASING.md

Version

Introduced in: v2.2.0

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free