ship
Skill1.7k starsChanged 7 months agoMITView on GitHub
Release engineering — sync main, run tests, audit coverage, push branch, open PR. Bootstraps test frameworks if needed. One command from "code complete" to "PR ready for review".
- Commits and pushes
194 other projects use a version of this.
Trending
Quiet since February.thin dataabout the whole repository
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
Who's talking about DenchHQ/ironclaw
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use ios-sync, open-gstack-browser and 8 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
ShreyRaviSkillsetup-gbrain
Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)
Also in 7 projects that use this
- +1 more from ShreyRavi
Other versions194 projects use a version of this.
Word for word · 1
- DenchHQ/DenchClaw★ 1.7k100% same
Edited · 0
None found.
Wrote their own version · 193
- 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
183 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 repository35 other files it gives its agents.
- .cursor/rules/git-rules.mdcCursor rule
- agent-builderSkill
- data-builderSkill
- game-builderSkill
- platform-apiSkill
- app-builderSkill
- composio-appsSkill
- actionsSkill
- documentsSkill
- duckdb-operationsSkill
- object-builderSkill
- reportsSkill
- database-crm-systemSkill
- views-filtersSkill
- dench-integrationsSkill
- benchmarkSkill
- canarySkill
- carefulSkill
- design-consultationSkill
- design-reviewSkill
- document-releaseSkill
- freezeSkill
- guardSkill
- investigateSkill
- land-and-deploySkill
- office-hoursSkill
- plan-ceo-reviewSkill
- plan-design-reviewSkill
- plan-eng-reviewSkill
- qa-onlySkill
- qaSkill
- retroSkill
- reviewSkill
- gstack-workflowSkill
- unfreezeSkill
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 179 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 32
If conflicts: resolve them.
- Distinctive: line 47
All tests must pass: If tests fail:
- Distinctive: line 49
Read the failure output
- Distinctive: line 52
If stuck after 3 attempts, ask the user
- Distinctive: line 58
Check test coverage for files changed in this branch:
- Distinctive: line 78
If missing tests, write them before proceeding (unless the user explicitly opts out).
- Distinctive: line 96
Labels: If applicable (bug, feature, refactor)
- Distinctive: line 127
After the PR is approved, use land-and-deploy to merge and deploy.
“Common” is measured: kept by at least 6 in 10 of the 179 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 — From Code Complete to PR
You are the release engineer. Take this branch from "done coding" to "PR ready for review."
Related skills: review | land-and-deploy | qa
Step 0: Detect Base Branch
gh pr view --json baseRefName -q .baseRefName- Fallback:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name - Fallback:
main
Step 1: Sync with Base
git fetch origin <base> --quiet
git merge origin/<base> --no-editIf conflicts: resolve them. If complex conflicts, ask the user.
Step 2: Run Tests
# Detect and run the project's test suite
npm test # Node.js
bundle exec rake # Ruby
pytest # Python
go test ./... # Go
cargo test # RustAll tests must pass. If tests fail:
- Read the failure output
- Fix the failing test (if it's a real bug, fix the bug)
- Re-run tests
- If stuck after 3 attempts, ask the user
Step 3: Coverage Audit
Check test coverage for files changed in this branch:
git diff origin/<base> --name-onlyFor each changed file, check if corresponding tests exist. Flag gaps:
COVERAGE AUDIT
═══════════════════════════════════════
Changed files: 12
With tests: 9
Missing tests: 3
- src/services/billing.ts (new service, no tests)
- src/utils/formatter.ts (new utility, no tests)
- src/api/webhook.ts (new endpoint, no tests)
═══════════════════════════════════════If missing tests, write them before proceeding (unless the user explicitly opts out).
Step 4: Push Branch
git push -u origin HEADStep 5: Create PR
Generate a PR with:
- Title: Concise description of the change
- Body: What changed, why, and how to test
- Labels: If applicable (bug, feature, refactor)
gh pr create --title "..." --body "..."Step 6: Post-Ship Checklist
- Tests pass
- Coverage gaps addressed or acknowledged
- No uncommitted changes
- PR description is clear
- Documentation updated (suggest document-release if needed)
Output
SHIP REPORT
═══════════════════════════════════════
Branch: feature/my-feature
Base: main
Tests: 42 pass, 0 fail
Coverage: +9 new tests
PR: github.com/org/repo/pull/123
═══════════════════════════════════════After the PR is approved, use land-and-deploy to merge and deploy.
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.

