agentleFS
Sign inStart free
theRizwantheRizwan/skills/skills/productivity/release-checklist/SKILL.md

release-checklist

Skill1 starsChanged 3 months agoMITView on GitHub

Run the pre-release checks for a package before publishing — version, changelog, build output, provenance, and the rollback plan. Use when about to cut a release or publish to a registry.

31 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

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 1

    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. Very specific:

    Read the file list. Are the build outputs there?

    line 27
  2. Distinctive:

    Verify the published artifact installs from the registry in a clean directory.

    line 48

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

The expensive release mistakes are all preventable in about ten minutes, and all much harder to undo than to prevent — most registries do not allow republishing a version number.

Before you tag

  • Working tree clean, on the release branch, up to date with the remote.
  • CI green on this exact commit, not on an earlier one.
  • Version bumped and matching the tag you are about to create.
  • Changelog updated with real entries. "Bug fixes" helps nobody; name what changed and link the PRs.
  • Breaking changes, if any, are a major bump. If you are arguing with yourself about whether something is breaking, it is breaking.

Check what actually ships

The most common release bug is shipping the wrong files.

npm pack --dry-run

Read the file list. Are the build outputs there? Are tests, fixtures, source maps and CI config not there, unless you meant them to be? Is the main/module/ exports map pointing at files that exist in that list?

Then install the tarball into a scratch project and import it. A package that builds is not the same as a package that resolves.

Publish with provenance

Publish from CI on a tag, not from a laptop. It gives you a signed provenance attestation, a reproducible record of what was built from which commit, and it removes the class of incident where a local uncommitted change ships.

Write the rollback before you need it

Know, in advance, which of these applies: deprecate the version, publish a patch, or move the dist-tag back. Decide now — the decision is much worse under pressure with users reporting breakage.

After publishing

Verify the published artifact installs from the registry in a clean directory. Then record it in your [[contribution-log]].

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