agentleFS
Sign inStart free
IcodeNetIcodeNet/agent-skills/skills/release/SKILL.md

release

Skill0 starsChanged 4 months agoMITView on GitHub

Prepare a release: decide the semantic version bump, write the changelog / release notes from actual changes, and tag. Use when releasing or publishing a package or service version, cutting a release branch, or when asked "what version should this be" or to write release notes. Do not use for the deploy execution itself (use deploy-checklist).

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

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a breaking change is present without a migration path documented, stop — that's a contract-guard failure to resolve before releasing, …

    line 29
  2. Very specific:

    Update the changelog file if the repo keeps one (CHANGELOG.md) — append, never rewrite history of prior releases.

    line 54
  3. Distinctive:

    Never publish a major bump silently as minor "to avoid alarm" — mislabeled breaking changes are the worst outcome for consumers.

    line 60
  4. Distinctive:

    If the project uses conventional commits or a release tool (changesets, semantic-release), follow that convention instead of hand-rolling.

    line 62

“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

A release is a statement to consumers: what changed, whether it's safe to upgrade, and what they must do if not.

Workflow

1. Collect the actual changes

Work from evidence, not memory: git log <last-release-tag>..HEAD plus the diff. Group commits into user-facing changes; ignore internal noise (CI tweaks, formatting) unless it affects consumers.

2. Decide the version bump

Apply the contract-guard classification (see the contract-guard skill and its breaking-change taxonomy) to everything in the release:

  • Any breaking change to a public surface → major
  • Compatible new capability → minor
  • Behavior-preserving fixes only → patch

If a breaking change is present without a migration path documented, stop — that's a contract-guard failure to resolve before releasing, not a notes problem.

3. Write the notes

Structure, plain language, consumer perspective:

## <version> — <date>

### Breaking changes        <!-- omit section if none -->
- <what broke> — **Migration:** <exact steps for the consumer>

### Added
- <new capability, phrased as what the user can now do>

### Fixed
- <symptom that no longer occurs>

### Changed / Deprecated    <!-- include deprecation timelines -->

Rules: every breaking entry has a migration step; entries describe outcomes, not commit titles; link issues/PRs where they exist.

4. Tag and record

  • Update the changelog file if the repo keeps one (CHANGELOG.md) — append, never rewrite history of prior releases.
  • Bump the version where the project declares it (package manifest, plugin manifest, etc.).
  • git tag v<version> after the release commit; push tags.

Constraints

  • Never publish a major bump silently as minor "to avoid alarm" — mislabeled breaking changes are the worst outcome for consumers.
  • Notes are for consumers, not contributors: no internal refactor bragging unless it changes observable behavior or performance.
  • If the project uses conventional commits or a release tool (changesets, semantic-release), follow that convention instead of hand-rolling.

Verification

  • Change list derived from git history since last tag
  • Bump justified against the breaking-change taxonomy
  • Every breaking change has a migration step
  • Version bumped in the manifest + changelog updated + tag created

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