ship
Skill4 starsChanged 5 months agoMITView on GitHub
Pre-deploy gate, deploy, and smoke-test in one pass — runs build/checks, deploys (Vercel by default), then verifies the live URL actually works. For shipping with confidence.
194 other projects use a version of this.
Adopted by
Most recently taken up by
- wboayue/rust-ibapitheir own version, first seen Nov 9, 2026
- haiggoh/run-to-completiontheir own version, first seen Nov 8, 2026
- sanmidable/skillstheir own version, first seen Nov 8, 2026
- Yesterday-AI/ytstacktheir own version, first seen Nov 8, 2026
- gaoyu06/harnesstheir own version, first seen Nov 8, 2026
- PeanutGT/NutsSkillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ios-sync, open-gstack-browser 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.
Saqlain-811Skillios-sync
Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Also in 6 projects that use this
seek888Skillopen-gstack-browser
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
Also in 10 projects that use this
ayudaySkillsetup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
Also in 19 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 9 projects that use this
zebbernSkilldebug-fix
Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)
Also in 4 projects that use this
ramybarsoumSkilldocument-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.
Also in 23 projects that use this
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- garrytan/gstack★ 141ksame name
- rtk-ai/rtk★ 86ksame name
- simstudioai/sim★ 30ksame name
- millionco/react-doctor★ 15ksame name
- BuilderIO/agent-native★ 7.6ksame name
- nightly-labs/openbot★ 6.3ksame name
- fallow-rs/fallow★ 5.3ksame name
- puncsky/system-design-and-architecture★ 3.6ksame name
- plugin87/ux-ui-agent-skills★ 3.1ksame name
- ShenSeanChen/waku-agent★ 2ksame name
184 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 repository18 other files it gives its agents.
- biz-validateSkill
- braindumpSkill
- catch-upSkill
- clone-websiteSkill
- double-checkSkill
- explain-for-grandmaSkill
- heavy-buildSkill
- heavy-reviewSkill
- heavySkill
- make-promptSkill
- monitor-claudeSkill
- orientSkill
- overnightSkill
- reelSkill
- sanity-checkSkill
- save-sessionSkill
- what-breaksSkill
- yt-tranSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 180 edited versions we read keep these.
4
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
- Very specific: line 11
Check the project for its own deploy tooling first (vercel.json, netlify.toml, Dockerfile, a deploy script in package.json, CI config).
- Distinctive: line 14
Run only what the project actually has, in order:
- Distinctive: line 18
If any hard gate fails, STOP and report the failure.
- Distinctive: line 24
Never trust "deploy succeeded" alone.
- Distinctive: line 32
Keep it tight. Never claim "shipped" if the smoke test didn't pass.
“Common” is measured: kept by at least 6 in 10 of the 180 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
Take the current project from "I think it's done" to "verified live." Do not deploy until the pre-checks pass. A broken deploy is not acceptable.
Step 0 — Identify the deploy path
Check the project for its own deploy tooling first (vercel.json, netlify.toml, Dockerfile, a deploy script in package.json, CI config). Default to Vercel CLI if nothing else is specified. Confirm the target: preview by default, production only if the user said so ($ARGUMENTS).
Step 1 — Pre-flight gate (block on failure)
Run only what the project actually has, in order:
- Install deps if needed — use the project's package manager (pnpm/npm/yarn per lockfile).
- Typecheck / lint / build — a passing build is the hard gate.
- Tests if present. If any hard gate fails, STOP and report the failure. Do not deploy.
Step 2 — Deploy
Before a production deploy, confirm with the user first — it's outward-facing and hard to undo. Preview deploys may proceed without asking. Run the deploy (vercel for preview, vercel --prod for production, or the project's own command) and capture the deployment URL. If the CLI needs login or project-linking, surface that to the user instead of hanging on the prompt.
Step 3 — Smoke-test the live deployment
Never trust "deploy succeeded" alone. Hit the actual URL (WebFetch / curl):
- Main page returns 200 with real content (not an error/placeholder page).
- One or two key routes if obvious.
Step 4 — Report
- Gate results (build/tests).
- Deployed URL + target.
- Smoke-test verdict: **Live and verified ** or **Deployed but smoke-test failed — investigate **. Keep it tight. Never claim "shipped" if the smoke test didn't pass.
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.