shipping
Skill3 starsChanged 29 days agoMITView on GitHub
Prepare and execute an authorized release with a checked recovery path. Triggers on "ship", "上线".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Pixxle/skillstheir own version, first seen Nov 1, 2026
- iha2/superlitetheir own version, first seen Nov 1, 2026
- cloud-f1/symphony-workflowtheir own version, first seen Oct 15, 2026
- soreavis/ai-docenttheir own version, first seen Oct 13, 2026
- sivori/seaworthytheir own version, first seen Oct 5, 2026
- calebnewtonusc/Chewbaccatheir own version, first seen Aug 11, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- microsoft/fast★ 9.7ksame name
- iha2/superlite★ 249same name
- calebnewtonusc/Chewbacca★ 8same name
- Pixxle/skills★ 1same name
- theYahia/cdek-mcp★ 1same name
- cloud-f1/symphony-workflow★ 0same name
- sivori/seaworthy★ 0same name
- soreavis/ai-docent★ 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- oss-strategySkill
- specSkill
- researchSkill
- api-designSkill
- architectureSkill
- codebase-designSkill
- design-researchSkill
- domain-modelingSkill
- frontend-designSkill
- imagegenSkill
- image-to-codeSkill
- prompt-engineeringSkill
- prototypeSkill
- schema-designSkill
- auth-implementationSkill
- breakdownSkill
- context-engineeringSkill
- error-handlingSkill
- i18nSkill
- implementSkill
- multi-agent-orchestrationSkill
- cost-optimizationSkill
- performanceSkill
- refactoringSkill
- simplifySkill
- api-testingSkill
- e2e-testingSkill
- load-testingSkill
- tddSkill
- test-generationSkill
- a11y-reviewSkill
- code-reviewSkill
- debuggingSkill
- lintingSkill
- security-reviewSkill
- ci-cdSkill
- deprecation-migrationSkill
- git-workflowSkill
- oss-polishSkill
- documentation-auditSkill
- handoffSkill
- incident-responseSkill
- observabilitySkill
- purity-auditSkill
- skill-authoringSkill
- using-skillsSkill
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 7 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 18
Verify builds, tests, config and migrations.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Shipping and Launch
When to use
- Prepare and execute an authorized release with a checked recovery path.
Not for: ci-cd for pipeline design; git-workflow for commits.
Steps
- Identify artifact, environment, authority, consumers and acceptable conditions.
- Verify builds, tests, config and migrations; define checks, stop conditions and rollback or forward recovery.
- Choose rollout proportional to risk and traffic, without universal canary percentages or fixed monitoring windows.
- Execute only authorized actions and inspect real health, critical flows and telemetry; recover when conditions are violated.
Output: Suggested paths, subject to human audit: docs/launch/rollback-plan.md when a separate recovery document is useful.
Verify
- Platform and artifact-specific recovery is concrete; actual evidence supports release claims and unexecuted actions stay explicit.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- human-audit.md — document consent, readability and human review.
- references/launch-monitoring.md — what to monitor at launch (application p50/p95/p99, infrastructure CPU/DB-pool/disk, client Core Web Vitals/JS errors) + ErrorBoundary and error-middleware scaffolding
- references/changelog-and-release-notes.md — commit history → categorized changelog (keepachangelog) → user-language release notes
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.