How do I install the Ship skill?

Run npx skillmds@latest add zebbern/ship in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ship skill do?

Scan changes, commit, push, and create a PR — with confirmation at each step It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ship?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

zebbern (@zebbern) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ship by zebbern — Agent Skill

Name: Ship
Author: zebbern

File contents

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 status to see all changed, staged, and untracked files
Run git diff to see what changed (staged + unstaged)
Run git log --oneline -5 to 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
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

---name: shipdescription: Scan changes, commit, push, and create a PR — with confirmation at each step---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 status` to see all changed, staged, and untracked files- Run `git diff` to see what changed (staged + unstaged)- Run `git log --oneline -5` to 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`- 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

Frequently asked questions

Ship