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
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- erikdarlingdata/PerformanceMonitortheir own version, first seen Nov 11, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- TrueImmortal82/open-code-skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- OneByJorah/VirtOfficetheir own version, first seen Nov 1, 2026
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.
CoralGameSkillplaytest-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
lilangMaxSkillsoak-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
lilangMaxSkillteam-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
CoralGameSkillteam-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
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- maximhq/bifrost★ 9.6ksame name
- tsukumijima/KonomiTV★ 1.1ksame name
- erikdarlingdata/PerformanceMonitor★ 536same name
- nkarasiak/qgis-mcp★ 364same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- OneByJorah/offivo★ 24same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- api-endpoint-testerSkill
- changelog-generatorSkill
- commit-message-writerSkill
- cron-explainerSkill
- csv-profilerSkill
- docker-compose-reviewerSkill
- dockerfile-linterSkill
- env-file-auditorSkill
- git-conflict-resolverSkill
- incident-postmortem-writerSkill
- json-diffSkill
- jwt-inspectorSkill
- log-analyzerSkill
- markdown-link-checkerSkill
- meeting-notes-to-actionsSkill
- openapi-summarizerSkill
- pr-description-writerSkill
- python-code-smellsSkill
- readme-doctorSkill
- regex-explainerSkill
- requirements-auditorSkill
- secure-code-reviewSkill
- skill-authorSkill
- sql-query-reviewerSkill
- todo-extractorSkill
- unit-test-writerSkill
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
- Distinctive: line 23
Ask or find out: what is being released (library, service, app), where it is published (PyPI, npm, a registry, a store, a server), and …
- Distinctive: line 33
Search the repository for the old number.
- Very specific: line 38
Commit and tag: Use an annotated or signed tag that matches the version (v1.4.0).
- Distinctive: line 39
Publish: Prefer automated publishing from CI with trusted credentials over publishing from a laptop.
- Distinctive: line 43
Announce: only after step 10 passes.
- Distinctive: line 47
Do not delete or re-use a published version number.
- Distinctive: line 49
Write down what failed and add a check to this list.
- Distinctive: line 53
If the publish target or version rules are unknown, ask before running any command that pushes tags or uploads files.
“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.
Files
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
- Branch is clean. Releasing from the default branch, no uncommitted changes, up to date with the remote.
- CI is green on the commit to be released. Do not release on a red or unknown build.
- Decide the version. Breaking change: major. New feature: minor. Fix only: patch. For
0.xprojects, say what the project treats as breaking. - Update the version in every place it lives (package metadata, a
__version__constant, docs, lock files). Search the repository for the old number. - Update the changelog. Group entries (added, changed, fixed, removed), mention breaking changes first, date the section.
- 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.
- Commit and tag. Use an annotated or signed tag that matches the version (
v1.4.0). Push the commit, then the tag. - Publish. Prefer automated publishing from CI with trusted credentials over publishing from a laptop.
- Create the release notes from the changelog section.
- Verify after release. Install the published version, run it, check that the docs and the package page show the new version.
- 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.
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
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.

