agentleFS
helmut-hoffer-von-ankershoffenhelmut-hoffer-von-ankershoffen/heinzel/.claude/skills/release/SKILL.md

release

Skill2 starsChanged 16 days agoMITView on GitHub

Cut a Heinzelmännchen release - semantic version from conventional commits, changelog, tag, GitHub release with provenance. Use when asked to release, publish or tag a version.

193 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

  • 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

  • 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

    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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 1

    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:

    Make sure main is green in CI and up to date locally.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 183 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

Releases are cut from main by automation; never edit versions or CHANGELOG.md by hand.

An automatic release finalizes an already staged candidate version when it is ahead of the highest reachable release tag. Otherwise it uses the conventional-commit suggestion. A forced bump advances the version currently in project metadata instead.

  1. Make sure main is green in CI and up to date locally.
  2. Preview: make changelog shows unreleased entries; uv run git-cliff --bumped-version shows the conventional version suggestion. The staged-candidate rule above can override that suggestion.
  3. Open the release pull request: make release INTRO="What changed for users." (BUMP=minor for a minor release) or Actions → Prepare release → Run workflow (bump auto, or force patch/minor/major): a GitHub runner prepares it, nothing runs locally (make release-local INTRO="What changed for users." is the local path). Every release requires an introduction: a few sentences on what changed for users, as the intro input or INTRO="...".
  4. Review the pull request chore(release): vX.Y.Z (version bumps, CHANGELOG.md, the introduction under the new heading; introductions of earlier releases are kept); CI runs on it; a maintainer reviews it and its current-head checks before merging.
  5. Release tag tags the merge commit and Publish builds, attests and creates the GitHub release: gh run watch.
  6. Verify: uv tool install --force git+https://github.com/helmut-hoffer-von-ankershoffen/heinzel@vX.Y.Z, then hz --version and hz system changelog.

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.