agentleFS
Lethe044Lethe044/agentskill-kit/skills/release-checklist/SKILL.md

release-checklist

Skill50 starsChanged 21 days agoMITView on GitHub

Walks through a software release step by step, from version bump and changelog to tagging, publishing and post-release checks. Use when the user is about to cut a release, asks what to verify before shipping, or wants a repeatable release process for a library or service.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, soak-test 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.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 12 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 14 projects that use this

  • +4 more from lilangMax
  • +4 more from CoralGame

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask or find out: what is being released (library, service, app), where it is published (PyPI, npm, a registry, a store, a server), and …

    line 23
  2. Distinctive:

    Search the repository for the old number.

    line 33
  3. Very specific:

    Commit and tag: Use an annotated or signed tag that matches the version (v1.4.0).

    line 38
  4. Distinctive:

    Publish: Prefer automated publishing from CI with trusted credentials over publishing from a laptop.

    line 39
  5. Distinctive:

    Announce: only after step 10 passes.

    line 43
  6. Distinctive:

    Do not delete or re-use a published version number.

    line 47
  7. Distinctive:

    Write down what failed and add a check to this list.

    line 49
  8. Distinctive:

    If the publish target or version rules are unknown, ask before running any command that pushes tags or uploads files.

    line 53

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

A release is a sequence of small checks. Do them in order and stop at the first failure.

When to use

  • The user says "let's release" or asks what is left before shipping.
  • A project has no written release process.
  • A release went wrong and the user wants a safer routine.

Before you start

Ask or find out: what is being released (library, service, app), where it is published (PyPI, npm, a registry, a store, a server), and whether versions follow semantic versioning.

Checklist

  1. Branch is clean. Releasing from the default branch, no uncommitted changes, up to date with the remote.
  2. CI is green on the commit to be released. Do not release on a red or unknown build.
  3. Decide the version. Breaking change: major. New feature: minor. Fix only: patch. For 0.x projects, say what the project treats as breaking.
  4. Update the version in every place it lives (package metadata, a __version__ constant, docs, lock files). Search the repository for the old number.
  5. Update the changelog. Group entries (added, changed, fixed, removed), mention breaking changes first, date the section.
  6. Run the full test suite and a fresh install test: build the package, install it in a clean environment and run the main command or import.
  7. Commit and tag. Use an annotated or signed tag that matches the version (v1.4.0). Push the commit, then the tag.
  8. Publish. Prefer automated publishing from CI with trusted credentials over publishing from a laptop.
  9. Create the release notes from the changelog section.
  10. Verify after release. Install the published version, run it, check that the docs and the package page show the new version.
  11. Announce only after step 10 passes.

If something goes wrong

  • Do not delete or re-use a published version number. Publish a new patch version.
  • Yank or deprecate the bad version if the registry supports it, and say why in the notes.
  • Write down what failed and add a check to this list.

Errors

If the publish target or version rules are unknown, ask before running any command that pushes tags or uploads files.

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.