ship
Skill44 starsChanged 6 months agoMITView on GitHub
Ship — commit and push in one command. Chains quality gates, conventional commit, push, and optional PR creation + merge. Use when the user says "ship", "commit and push", "/ship", or wants to finalize a branch.
- Reads credentials
- Commits and pushes
194 other projects use a version of this.
Adopted by
Most recently taken up by
- Robo-Co-op/robobuilder-standardtheir own version, first seen Nov 16, 2026
- zyggy-org/zyggytheir own version, first seen Nov 16, 2026
- champ18ion/claud18codetheir own version, first seen Nov 16, 2026
- joelhooks/uncomplecttheir own version, first seen Nov 16, 2026
- claudialnathan/skillstheir own version, first seen Nov 15, 2026
- saleem-hadad/skillstheir own version, first seen Nov 15, 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★ 142ksame name
- rtk-ai/rtk★ 87ksame name
- simstudioai/sim★ 30ksame name
- millionco/react-doctor★ 15ksame name
- nightly-labs/openbot★ 7.9ksame name
- BuilderIO/agent-native★ 7.7ksame name
- fallow-rs/fallow★ 5.4ksame name
- puncsky/system-design-and-architecture★ 3.6ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- ShenSeanChen/waku-agent★ 2.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 repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-creatorSkill
- anti-overengineeringSkill
- audit-docsSkill
- auto-reviewSkill
- architectureSkill
- clean-codeSkill
- commitSkill
- create-docSkill
- dddSkill
- discoverySkill
- docs-indexSkill
- e2eSkill
- event-stormingSkill
- implement-featureSkill
- product-managerSkill
- refactor-featureSkill
- refactoring-mikado-stranglerSkill
- review-backSkill
- review-docSkill
- review-followupSkill
- review-frontSkill
- review-fullstackSkill
- securitySkill
- skill-creatorSkill
- solidSkill
- dashboard-stylingSkill
- tddSkill
- update-docsSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 47
If branch = master: STOP — the protect-main-push.sh hook blocks push to master.
- Distinctive: line 48
If nothing to commit: inform and stop.
- Distinctive: line 54
If files are not staged, list them and add them by name (never git add -A or git add .)
- Distinctive: line 141
ONLY if the user explicitly asked for merge: Never merge without explicit confirmation.
- Very specific: line 162
NEVER: use --force push
- Very specific: line 164
NEVER: use --no-verify or bypass hooks
- Very specific: line 165
NEVER: commit .env, credentials, or secrets
- Distinctive: line 167
ALWAYS: verify you are on a feature branch before pushing
“Common” is measured: kept by at least 6 in 10 of the 181 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 — Commit & Push
Activation
This skill activates with /ship. It chains verification, commit, push, and optionally PR creation and merge.
Optional arguments
/ship # Commit + push (no PR)
/ship pr # Commit + push + gh pr create
/ship pr merge # Commit + push + gh pr create + gh pr merge --admin --squashWorkflow
Step 0: Quality Gates (BLOCKING)
BEFORE any commit, run:
yarn verifyyarn verify runs: TypeScript check + Biome lint + Vitest tests.
If it fails: display the errors and STOP. Do not proceed until all quality gates pass.
Step 1: Analysis
git status --short
git branch --show-current
git log --oneline -5Guards:
- If branch =
master: STOP — theprotect-main-push.shhook blocks push to master. Create a feature branch first. - If nothing to commit: inform and stop.
Step 2: Staging
- If files are not staged, list them and add them by name (never
git add -Aorgit add .) - NEVER include
.env, credentials, secrets, or lock files unless explicitly requested - NEVER include files unrelated to the current change
Preferred pattern:
git add src/usecases/foo.usecase.ts src/tests/units/usecases/foo.usecase.test.tsStep 3: Commit
Infer the message from the staged changes. Follow Conventional Commits:
<type>(<scope>): <description>| Type | Usage |
feat | New feature |
fix | Bug fix |
refactor | Refactoring (no feature or fix) |
test | Tests only |
docs | Documentation only |
chore | Maintenance, dependencies |
style | Formatting (no logic change) |
perf | Performance improvement |
ci | CI/CD changes |
Rules:
- Header max 72 characters
- Description in lowercase, no trailing period
- Scope optional in parentheses, must match bounded context name when applicable
Commit via heredoc (preserves formatting):
git commit -m "$(cat <<'EOF'
feat(webhook): add GitHub signature validation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"The pre-commit-gate.sh and verify-spec-updated.sh hooks run automatically. If they fail, fix the issue and retry — never use --no-verify.
Step 4: Push
git push -u origin <branch>The protect-main-push.sh hook blocks push to master and force push. If it triggers, verify you are on a feature branch.
Step 5 (if pr or pr merge): Create PR
gh pr create --title "<type>(<scope>): <description>" --body "$(cat <<'EOF'
## Summary
- <bullet point 1>
- <bullet point 2>
## Test plan
- [ ] yarn verify passes
- [ ] Acceptance tests green
🤖 Generated with Claude Code
EOF
)"Base branch: master.
Step 6 (if pr merge only and user explicitly requested): Merge PR
gh pr merge --admin --squashONLY if the user explicitly asked for merge. Never merge without explicit confirmation.
Step 7: Summary
SHIP
Branch : <branch>
Commit : <type>(<scope>): <description>
Push : origin/<branch>
Gates : yarn verify — green
PR : <url or "not created">
Merge : <squash merged or "not merged">Security Rules
- NEVER use
--forcepush - NEVER push to
masterdirectly (hook enforces this) - NEVER use
--no-verifyor bypass hooks - NEVER commit
.env, credentials, or secrets - NEVER stage with
git add -Aorgit add . - ALWAYS verify you are on a feature branch before pushing
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.

