ship-checklist
Skill1 starsChanged 41 days agoMITView on GitHub
Run a pre-ship launch checklist before production. Use when releasing, enabling feature flags, or preparing a rollout.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Alfred-Lau/skillstheir own version, first seen Oct 20, 2026
- royalpinto007/ship-skillstheir own version, first seen Oct 13, 2026
- Zwin-ux/kittheir own version, first seen Oct 11, 2026
- jammyfu/open-game-skillstheir own version, first seen Oct 11, 2026
- Necmttn/axtheir own version, first seen Jun 12, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Necmttn/ax★ 116same name
- jammyfu/open-game-skills★ 12same name
- Alfred-Lau/skills★ 1same name
- royalpinto007/ship-skills★ 1same name
- Zwin-ux/kit★ 0same name
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 repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- browser-verifySkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- debug-systematicSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- incremental-slicesSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- react-componentsSkill
- refactor-safeSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- spec-drivenSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
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 30
Do not ship with failing required checks.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Ship Checklist
Before Prod
- Acceptance checks from the spec are green
- Migrations are backward-compatible or staged
- Feature flag defaults are safe; rollback path known
- Observability: logs/metrics/alerts for the new path
- Secrets/config present in target env (not hardcoded)
- Performance-sensitive paths smoke-tested
- Security-sensitive changes reviewed
- Docs/runbook updated if operators are affected
- On-call knows the change window
Rollout
- Deploy quietly when possible (flag off).
- Enable for internal/canary first.
- Watch error rate, latency, and business KPIs.
- Expand or roll back based on signals.
Rules
- Prefer reversible releases.
- Do not ship with failing required checks.
- Record what was shipped (version/commit/flag).
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.