agentleFS
iamrohithrnairiamrohithrnair/merman/.claude/skills/release/SKILL.md

release

Skill42 starsChanged 18 days agoMITView on GitHub

Cut a merman release - version bump, changelog, verify, tag and push. Use when asked to "release", "bump the version", "ship 0.x" or "publish".

  • Commits and pushes

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

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Generated files: if scripts/package.json changed, run npm --prefix scripts run build:vendor, and confirm the bundle has no import …

    line 11
  2. Very specific:

    Verify: run every step in AGENTS.md Verify, plus live-check of /merman demo and /merman demo-rtl, reading every Hebrew line right to left.

    line 12

“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

  1. Pick the version. Breaking option or token renames are minor while below 1.0 (and major after). New features are minor. Fixes are patch.
  2. Set it in both manifests: version in .claude-plugin/plugin.json and plugins[0].version in .claude-plugin/marketplace.json. Leave the marketplace source on the previous tag until step 9.
  3. Changelog: add a dated ## [x.y.z] at the top of docs/CHANGELOG.md, with Added, Changed and Fixed written for users. Write it from the "What changes for the user" section of every PR or commit since the last tag (git log vPREV..HEAD --oneline), one entry per user-visible change. Fold in anything still under ## [Unreleased] and drop that heading.
  4. Generated files: if scripts/package.json changed, run npm --prefix scripts run build:vendor, and confirm the bundle has no import statements and no non-MIT code (grep -c -i elk hooks/vendor/*.js must print 0).
  5. Verify: run every step in AGENTS.md Verify, plus live-check of /merman demo and /merman demo-rtl, reading every Hebrew line right to left.
  6. Fresh install test against a throwaway config:
    mkdir -p <scratch>/fresh/skills && ln -s <repo> <scratch>/fresh/skills/merman
    CLAUDE_CONFIG_DIR=<scratch>/fresh claude plugin list
    It must show merman@skills-dir at the new version with Status: ✔ loaded.
  7. Push the release commit to main and wait for every CI job to pass.
  8. Tag main: git tag vX.Y.Z <release commit> && git push origin vX.Y.Z. The release workflow checks the tag against plugin.json, checks the tag is on main, and publishes the GitHub release from the CHANGELOG section.
  9. Pin the release: a second commit sets ref to vX.Y.Z and sha to the tagged commit (git rev-list -n1 vX.Y.Z) in the source of .claude-plugin/marketplace.json. Until it is pushed, marketplace installs keep getting the previous release. Then check a clean install from GitHub:
    CLAUDE_CONFIG_DIR=<scratch>/market claude plugin marketplace add iamrohithrnair/merman
    CLAUDE_CONFIG_DIR=<scratch>/market claude plugin install merman@merman
    CLAUDE_CONFIG_DIR=<scratch>/market claude plugin list
    It must show merman@merman at the new version, enabled.
  10. Confirm CI and the release workflow are green.

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.