ship
Skill2 starsChanged 6 months agoMITView on GitHub
Scan changes, commit, push, and create a PR. With confirmation at each step
- Reads credentials
- Commits and pushes
194 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- claudialnathan/skillstheir own version, first seen Nov 15, 2026
- saleem-hadad/skillstheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
- ShipfoxHQ/shipfoxtheir own version, first seen Nov 15, 2026
- nightly-labs/openbottheir own version, first seen Nov 14, 2026
Used with
Projects with it also use ios-sync, open-gstack-browser and 9 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
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
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 · 0
None found.
Edited · 2
- poshan0126/dotclaude★ 87163% same
- zebbern/termstack★ 4100% same
Wrote their own version · 192
- 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.3ksame name
- puncsky/system-design-and-architecture★ 3.6ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- ShenSeanChen/waku-agent★ 2.2ksame name
182 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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- context-budgetSkill
- debug-fixSkill
- explainSkill
- pr-reviewSkill
- refactorSkill
- setupdotclaudeSkill
- tddSkill
- test-writerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 14 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
3
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
- Distinctive: line 23
Run git status to see all changed, staged, and untracked files
- Distinctive: line 24
Run git diff to see what changed (staged + unstaged)
- Distinctive: line 25
Run git log --oneline -5 to see recent commit style
- Distinctive: line 31
If there are no changes, tell the user and stop
- Distinctive: line 44
Only after confirmation: stage the files and create the commit
- Distinctive: line 45
If the commit fails (e.g., pre-commit hook), fix the issue and try again with a NEW commit
- Distinctive: line 49
Check if the current branch has an upstream remote
- Very specific: line 50
If not, propose creating one with git push -u origin <branch>
- Distinctive: line 51
ASK the user to confirm: before pushing
- Distinctive: line 52
Only after confirmation: push to remote
- Very specific: line 56
Check if a PR already exists for this branch (gh pr view.
- Distinctive: line 60
Test plan: how to verify
- Very specific: line 62
Only after confirmation: create the PR with gh pr create
- Distinctive: line 67
NEVER skip a confirmation step.
- Distinctive: line 69
NEVER commit .env, secrets, or credential files
- Distinctive: line 70
If the user says "skip" at any step, skip that step and move to the next
- Distinctive: line 71
If $ARGUMENTS is provided, use it as the commit message / PR title
“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 the current changes through commit, push, and PR creation. Confirm with the user before each step using the AskUserQuestion tool.
Step 1: Scan
- Run
git statusto see all changed, staged, and untracked files - Run
git diffto see what changed (staged + unstaged) - Run
git log --oneline -5to see recent commit style - Present a clear summary to the user:
- Files modified
- Files added
- Files deleted
- Untracked files
- If there are no changes, tell the user and stop
Step 2: Stage & Commit
- Propose which files to stage. Never stage these:
- Secrets:
.env*,*.pem,*.key,credentials.json - Lock files:
package-lock.json,yarn.lock,pnpm-lock.yaml(unless intentionally updated) - Generated:
*.gen.ts,*.generated.*,*.min.js,*.min.css - Build output:
dist/,build/,.next/,__pycache__/ - Dependencies:
node_modules/,vendor/,.venv/ - OS/editor:
.DS_Store,Thumbs.db,*.swp,.idea/,.vscode/settings.json
- Secrets:
- Draft a commit message based on the changes, matching the repo's existing commit style
- ASK the user to confirm or edit: show the exact files to stage and the proposed commit message
- Only after confirmation: stage the files and create the commit
- If the commit fails (e.g., pre-commit hook), fix the issue and try again with a NEW commit
Step 3: Push
- Check if the current branch has an upstream remote
- If not, propose creating one with
git push -u origin <branch> - ASK the user to confirm before pushing
- Only after confirmation: push to remote
Step 4: Pull Request
- Check if a PR already exists for this branch (
gh pr view. If it exists, show the URL and stop) - Analyze ALL commits on this branch vs the base branch (not just the latest commit)
- Draft a PR title (under 72 chars) and body with:
- Summary: 2-4 bullet points
- Test plan: how to verify
- ASK the user to confirm or edit the title and body
- Only after confirmation: create the PR with
gh pr create - Show the PR URL when done
Rules
- NEVER skip a confirmation step. Each step requires explicit user approval
- NEVER force-push
- NEVER commit .env, secrets, or credential files
- If the user says "skip" at any step, skip that step and move to the next
- If $ARGUMENTS is provided, use it as the commit message / PR title
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.

