agentleFS
afittestideafittestide/asimi/.claude/skills/release/SKILL.md

release

Skill16 starsChanged 7 days agoMITView on GitHub

Run the full release process for asimi - update changelog, bump version, update roadmap, commit, and tag. Use when the user says "release", "cut a release", "prepare release", or similar.

  • 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

  • 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

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    If no version argument was provided, read the current version from line 34 of main.go (the var version line), determine the next …

    line 10
  2. Distinctive:

    Follow these steps in order:

    line 12
  3. Very specific:

    Read git log since the last tagged release: git log $(git describe --tags --abbrev=0)..HEAD --oneline

    line 17
  4. Very specific:

    Ensure all user-notable changes are listed under an ## Unreleased section

    line 18
  5. Distinctive:

    Read README.md and find the Roadmap section

    line 31
  6. Very specific:

    Check which issues referenced in the roadmap are now closed: gh issue list --state closed

    line 32
  7. Distinctive:

    Remove closed issues from the roadmap table

    line 33
  8. Very specific:

    Check for new open issues that should be on the roadmap: gh issue list --state open

    line 34
  9. Distinctive:

    Add relevant new open issues to the roadmap table using the format:

    line 35
  10. Distinctive:

    Do NOT push automatically — let the user decide when to push.

    line 62
  11. Distinctive:

    Use present progressive tense in changelog entries ("adding feature" not "added feature")

    line 66
  12. Distinctive:

    Do NOT push to remote — only commit and tag locally

    line 68
  13. Distinctive:

    Do NOT merge — ask user for approval at every significant step

    line 69

“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

You are releasing version $ARGUMENTS of asimi.

If no version argument was provided, read the current version from line 34 of main.go (the var version line), determine the next appropriate version by reviewing the CHANGELOG.md unreleased section, and ask the user to confirm before proceeding.

Follow these steps in order:

1. Prepare CHANGELOG.md

  • Read CHANGELOG.md
  • Read git log since the last tagged release: git log $(git describe --tags --abbrev=0)..HEAD --oneline
  • Ensure all user-notable changes are listed under an ## Unreleased section
  • Rename ## Unreleased to ## [$ARGUMENTS] - YYYY-MM-DD using today's date
  • Organize entries under: ### Added, ### Changed, ### Fixed, ### Removed (only include sections that have entries)

2. Update version in main.go

Edit line 34 in main.go to set:

var version = "$ARGUMENTS"

3. Update README.md Roadmap

  • Read README.md and find the Roadmap section
  • Check which issues referenced in the roadmap are now closed: gh issue list --state closed
  • Remove closed issues from the roadmap table
  • Check for new open issues that should be on the roadmap: gh issue list --state open
  • Add relevant new open issues to the roadmap table using the format:
    | [#XX - Feature Name](https://github.com/afittestide/asimi/issues/XX) | Brief description |

4. Show the user a summary of all changes and ask for approval before committing

Present a diff summary and wait for explicit user confirmation. DON'T commit or tag without approval.

5. Commit the release (only after user approval)

git add CHANGELOG.md main.go README.md
git commit -m "chore: releasing $ARGUMENTS"

6. Tag (only after user approval)

git tag -a v$ARGUMENTS -m "Release $ARGUMENTS"

Tell the user the tag is created locally. Remind them to push with:

git push origin main --tags

Do NOT push automatically — let the user decide when to push.

Important rules

  • Use present progressive tense in changelog entries ("adding feature" not "added feature")
  • Follow SemVer: major.minor.patch
  • Do NOT push to remote — only commit and tag locally
  • Do NOT merge — ask user for approval at every significant step

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.