release-checklist
Skill0 starsChanged 2 months agoMITView on GitHub
Use automatically before deploys, releases, publishing changes, production pushes, migrations, app launches, website launches, major merges, or when the user asks whether a project is ready to ship.
31 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- erikdarlingdata/PerformanceMonitortheir own version, first seen Oct 25, 2026
- juanitourquiza/shipframetheir own version, first seen Oct 23, 2026
- maximhq/bifrosttheir own version, first seen Oct 20, 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
- 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
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- maximhq/bifrost★ 9.4ksame name
- tsukumijima/KonomiTV★ 1.1ksame name
- erikdarlingdata/PerformanceMonitor★ 526same name
- nkarasiak/qgis-mcp★ 364same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 118same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- OneByJorah/offivo★ 24same name
21 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 repository5 other files it gives its agents.
- code-review-businessSkill
- landing-page-conversionSkill
- project-launch-checkSkill
- security-liteSkill
- seo-ai-search-safeSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use before shipping anything meaningful.
- Distinctive: line 15
verify no critical warnings
- Distinctive: line 18
run test suite if present
- Distinctive: line 19
run typecheck if present
- Distinctive: line 20
run lint if present
- Distinctive: line 21
do not invent success if commands fail
- Distinctive: line 26
use Playwright for web apps when useful
- Distinctive: line 75
Never say "ready" without evidence.
“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.
Files
Release Checklist
Use before shipping anything meaningful.
Required checks
- Build
- install dependencies
- run build
- verify no critical warnings
- Tests
- run test suite if present
- run typecheck if present
- run lint if present
- do not invent success if commands fail
- Runtime verification
- launch the app
- verify main flows
- use Playwright for web apps when useful
- check console errors
- check network errors
- Environment
- required env vars
- secrets not committed
- API keys not exposed
- production/staging separation
- Database
- migrations reviewed
- rollback plan
- backup if risky
- RLS/policies checked for Supabase
- Observability
- Sentry/error tracking if available
- logs
- analytics
- critical events
- Security
- auth
- permissions
- public endpoints
- upload handling
- rate limits where needed
- Performance
- obvious slow paths
- large bundles
- image optimization
- mobile performance
- Rollback
- how to undo
- what to monitor after deploy
Output format
- Ready/not ready verdict
- Blocking issues
- Non-blocking issues
- Commands run
- Evidence of verification
- Release notes
- Rollback plan
Never say "ready" without evidence.
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.