agentleFS
stormlightlabsstormlightlabs/thunderus/.claude/skills/release/SKILL.md

release

Skill4 starsChanged 57 days agoApache-2.0View on GitHub

Cut a release from edge to main, tag it, and publish. Use when asked to cut a release, ship a version, tag, or publish thndrs to crates.io.

  • 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

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 4

    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
  1. Distinctive:

    Every step here is outward-facing.

    line 11
  2. Distinctive:

    Stop unless all of these hold:

    line 17
  3. Very specific:

    No issue sits at status:review with an open pull request meant for this release.

    line 20
  4. Very specific:

    Update version in crates/thndrs/Cargo.toml and crates/thndrs-agent/Cargo.toml, then cargo update --workspace so Cargo.lock matches.

    line 48
  5. Very specific:

    Leave an empty ## Unreleased behind.

    line 63
  6. Very specific:

    Write for a user of thndrs: name the behavior that changed, not the module.

    line 65
  7. Very specific:

    Use the writing-docs skill.

    line 66
  8. Distinctive:

    Run what CI runs, before asking for the pull request:

    line 70
  9. Distinctive:

    After the merge, from main:

    line 96

“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

A release is one reviewed pull request from edge to main, a tag on main, and a publish. main matches the released tag between releases.

Every step here is outward-facing. Confirm with the user before the pull request, before the tag, and before the publish. Approval for one is not approval for the next.

Preconditions

Stop unless all of these hold:

  • edge is green on the required checks.
  • No issue sits at status:review with an open pull request meant for this release.
  • The working tree is clean. cargo package refuses a dirty tree, and forcing past that publishes files nobody reviewed.
gh run list --branch edge --limit 1
git status --short

Through MCP: actions_list method list_workflow_runs with workflow_runs_filter.branch set to edge.

Version

Both crates share a version. Decide it from the changes since the last tag, not from habit:

ChangeBump
Breaking API or behavior change before 1.0minor
New behavior, backward compatibleminor
Fixes and internal work onlypatch
git log --oneline "$(git describe --tags --abbrev=0)"..edge

Update version in crates/thndrs/Cargo.toml and crates/thndrs-agent/Cargo.toml, then cargo update --workspace so Cargo.lock matches.

Tags before the first release

The command above answers v0.1.1. v0.1.0 is unreachable from main and edge and never answers, which is not a broken tag. 0.1.1 is tagged and unpublished, so the check under After reports it against 0.1.0 on crates.io until a release publishes. Issue #3 records which commit each tag marks.

Changelog

Move ## Unreleased entries into a new ## <version> section with the date. Leave an empty ## Unreleased behind.

Write for a user of thndrs: name the behavior that changed, not the module. Use the writing-docs skill.

Verify

Run what CI runs, before asking for the pull request:

cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
cargo test --workspace --all-features --locked
cargo doc --workspace --all-features --no-deps --locked
pnpm --dir docs build
cargo package -p thndrs-agent --locked

Pull request

gh pr create --base main --head edge --title "release: v<version>" --body-file <file>
# MCP: create_pull_request with base "main", head "edge", and the body inline.

The body lists the user-visible changes and names the verification that ran. This is where a human reads the accumulated edge diff at outcome level, so it is the last point at which the release can be stopped cheaply.

A human merges it. Do not merge this pull request.

Tag and publish

After the merge, from main:

git checkout main && git pull
git tag "v<version>"
git push origin "v<version>"

Publish the library before the binary, because the binary depends on it:

cargo publish -p thndrs-agent --locked
cargo publish -p thndrs --locked

A publish cannot be undone. A version number cannot be reused. Confirm the version and the tag before running either command.

After

Move every issue at status:verify that shipped in this release to status:done through the github-board skill.

Confirm main, the tag, and the published version all name the same version. If they disagree, say so rather than reconciling quietly.

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.