agentleFS
Sign inStart free
agentdecksdkagentdecksdk/agentdeck/.claude/skills/release/SKILL.md

release

Skill4 starsChanged 2 months agoMITView on GitHub

Cut an agentdeck release - bump version, update CHANGELOG, merge dev to main, and tag vX.Y.Z.

  • Commits and pushes

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

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Follow the release process strictly.

    line 8
  2. Very specific:

    Preflight: Verify clean working tree, non-empty [Unreleased] section, and make check is 100% green.

    line 30
  3. Very specific:

    Run python scripts/generate_docs_reference.py once, then verify python scripts/generate_docs_reference.py --check.

    line 40
  4. Very specific:

    Commit: chore(release): vX.Y.Z.

    line 45
  5. Distinctive:

    Keep text between tool calls to ≤25 words.

    line 65

“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 agentdeck

Follow the release process strictly. All work starts on dev; main is release-only, and dev is the repository's default branch.

Two PRs, two issues

A release needs two labeled chore issues and two PRs, not one of each.

PRbaseissueclosing keyword
bumpdevits own labeled chore issueCloses #N, works: dev is default
promotionmainits own labeled chore issueRefs #N only, close by hand: main is not default, so GitHub never creates the closing reference

git push origin dev is rejected directly ("push declined due to repository rule violations"). The bump goes through its own PR into dev.

A PR body closing more than one issue needs one Fixes #N (or Closes #N) per line: GitHub's closing-keyword parser only recognizes the first reference in a comma-separated list, silently leaving the rest open (#541).

Release Steps

  1. Version: Confirm SemVer bump (pyproject.toml and CHANGELOG.md).
  2. Preflight: Verify clean working tree, non-empty [Unreleased] section, and make check is 100% green. Run it unpiped (make check, not make check | tail) so its own exit code is what you read; a pipe reports the last command's status, not the gate's.
  3. Bump issue: python scripts/release_bump.py issues X.Y.Z creates (or reuses) the vX.Y.Z milestone, assigns it to every issue closed by a PR merged since the last tag (read from that PR's closingIssuesReferences; a direct push falls back to scanning its message for Fixes/Closes), opens the labeled chore: cut and ship vX.Y.Z issue, and prints its number.
  4. Bump PR into dev:
    • python scripts/release_bump.py bump X.Y.Z updates pyproject.toml's version and moves CHANGELOG.md's [Unreleased] entries to a dated ## [X.Y.Z] heading with compare links.
    • Run python scripts/generate_docs_reference.py once, then verify python scripts/generate_docs_reference.py --check.
    • Snapshot the docs site only if this release removes or changes a documented surface, not on every release (docs/delivery/docs-site-plan.md DS-D3). A patch documenting the same surface owes nothing.
    • Commit: chore(release): vX.Y.Z. Open the PR against the bump issue from step 3 (Closes #N), wait for every required check, merge.
  5. Promotion issue: python scripts/release_bump.py promote X.Y.Z opens the labeled chore: release vX.Y.Z to main issue in the same milestone and prints its number.
  6. Promotion PR, dev to main: Open it against the promotion issue from step 5 (Refs #N). Issue hygiene, slop, and Check affected documentation skip themselves on a main-based PR: each already ran the real per-PR version of itself against dev at merge time, and this diff is the whole release cycle re-evaluated, not a new change. Wait for check and Build documentation, then merge and close the promotion issue by hand.
  7. Tag: git tag vX.Y.Z && git push origin vX.Y.Z. release.yml publishes to PyPI on this push; there is no undo once the tag lands.
  8. Close the milestone: python scripts/release_bump.py close-milestone X.Y.Z, right after the tag push. Every past release skipped this: v5.0.0 through v5.1.0 all shipped with 0 open issues but stayed open on GitHub.
  9. Deploy: In the prod/ worktree (detached on a tag on purpose, so the public only sees something released), run ./deploy-prod.sh vX.Y.Z. It rebuilds docs-site, restarts agentdeck-docs-static.service, and health-checks 127.0.0.1:4321.
  10. Report: Return the GitHub release URL.

Ground Rules

  • Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.

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