ship · raphaelsalaja — Claude Code skill: ship changes
A skill for Claude Code takes finished changes through commits, merges, releases and production checks. It runs when asked to push, merge or ship work.
MIT 167 installs ★ 69 updated 2026-11-14
npx skills add raphaelsalaja/skills --skill ship -a claude-codeWhat ship does
The skill checks the working tree, reviews changed files and commits each logical change separately. Commit messages follow Conventional Commits, and packages that publish releases get a changeset with the change. It pushes the branch and merges it when requested.
It waits for CI to finish and fixes failing checks. UI changes get a screenshot in the pull request; a fixed issue is linked, closed and answered. After deployment, the skill opens the live URL or published version and checks it.
Secrets and files changed outside the task are flagged before committing; a committed secret or stray file is a HIGH finding. The skill asks for a login, two-factor code or approval when a step needs one.
What it helps with
- split unrelated work into separate commits
- format commit messages as Conventional Commits
- wait for CI and address failed checks
- check a deployment and close its issue
Example prompts for the agent
- Push the finished changes and wait for CI checks to complete.
- Merge this branch, delete it, and switch back to the default branch.
- Release the fix, check the published version, and close its issue.
How to install ship
1Skills CLI (Vercel)
npx skills add raphaelsalaja/skills --skill ship -a claude-code2Manually: put the files in place
~/.claude/skills/ship/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ship/
1Skills CLI (Vercel)
npx skills add raphaelsalaja/skills --skill ship -a codex2Manually: put the files in place
.agents/skills/ship/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add raphaelsalaja/skills --skill ship -a cursor2Manually: put the files in place
.cursor/skills/ship/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install raphaelsalaja/skills skills/ship2Manually: put the files in place
.github/skills/ship/SKILL.md1Skills CLI (Vercel)
npx skills add raphaelsalaja/skills --skill ship -a gemini-cli2Platform CLI
gemini skills install https://github.com/raphaelsalaja/skills --path skills/shipManually: put the files in place
.devin/skills/ship/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add raphaelsalaja/skills --skill ship -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ship
How do I install ship in Claude Code?
Run npx skills add raphaelsalaja/skills --skill ship -a claude-code. The skill file is at ~/.claude/skills/ship/SKILL.md.
What does ship do?
It takes a change through commits, pushing, merging and CI, then checks the deployed result. It also links and closes the issue fixed by the change.
What does ship need to complete a release?
It can request a login, a two-factor code or approval when required. It handles the other steps itself.
Source text
SKILL.md · MIT
--- name: ship description: Commits, pushes, merges and releases a change, watches the checks and confirms it is live. disable-model-invocation: true --- # Ship This skill takes finished work from the working tree to production. It commits in small pieces, pushes, merges, watches checks and confirms the result is live. ## Push means push When the user says push, ship or merge, do every step to the end. Handing a command back to the user is a finding unless it needs their credentials or their approval. A secret in a commit is always `HIGH`. Checking the change itself runs in `verify` before this skill starts. ## 1. Check the tree Run `git status` and read every changed file. Name any file you did not change in this task and ask before committing it. Committing a stray file is `ship-flag-stray-files`. Scan the diff for keys, tokens, passwords and `.env` files. A committed secret is `ship-no-secrets`. ## 2. Commit per change Make one commit per logical change. One commit for a feature, a fix and a rename is `ship-commit-per-change`. Write every message as a Conventional Commit: `type(scope): summary` in the imperative, lowercase and with no full stop. Use `feat`, `fix`, `docs`, `refactor`, `chore` or another standard type, and mark a breaking change with `!` after the type. A message like "Remove the archive." is `ship-conventional-commits`. In a package that publishes releases, add the changeset with the change. A release-bound change with no changeset is `ship-changeset-for-packages`. ## 3. Push, merge and tidy Push the branch. When asked to merge, merge it, delete the branch and switch back to the default branch. A merged branch left behind is `ship-merge-and-tidy`. Open one pull request per bug or feature. A pull request bundling three fixes is `ship-one-pr-per-bug`. A pull request that changes UI carries a screenshot. That is `ship-screenshot-ui-prs`. ## 4. Watch the checks Wait for CI and fix what fails. Reporting "pushed" while checks are red or still running is `ship-watch-checks`. ## 5. Close the loop When the change fixes an issue, link it, close it and reply where it was raised. A fixed bug with its issue left open is `ship-close-the-loop`. When the change deploys, open the live URL or the published version and check it. "Deployed" with no look at production is `ship-confirm-live`. ## 6. Hand back only what needs the user Do every step you can run yourself. Ask only for a login, a two-factor code or an approval. Say exactly which. A list of commands for the user to run is `ship-do-the-steps`. ## The pair Every check is a pair. The broken line sits beside the line that replaces it. | Rule | Broken | Replacement | | --- | --- | --- | | `ship-flag-stray-files` | `git add -A` with someone else's file in the tree | The file named, then a question | | `ship-no-secrets` | `.env.local` committed | `.env.local` ignored, the secret flagged for rotation | | `ship-commit-per-change` | One commit for a feature, a fix and a rename | Three commits, one per change | | `ship-conventional-commits` | `Remove the archive.` | `chore: remove the archive` | | `ship-changeset-for-packages` | A package fix with no changeset | The changeset in the same commit | | `ship-merge-and-tidy` | Merged, the branch still checked out | Merged, deleted, back on `main` | | `ship-one-pr-per-bug` | One pull request for three bugs | Three pull requests | | `ship-screenshot-ui-prs` | A UI pull request with no image | A screenshot in the description | | `ship-watch-checks` | "Pushed" while CI runs | "Pushed, all checks pass" | | `ship-close-the-loop` | The fix merged, the issue open | The issue linked, closed and answered | | `ship-confirm-live` | "Deployed" | "Live at the production URL, checked" | | `ship-do-the-steps` | "Run `npm publish` when ready" | Published, or "needs your two-factor code" | ## Reporting **Severity.** `HIGH` is a committed secret, a stray file committed or a release with failing checks. `MEDIUM` is a bundled commit or pull request, an open issue after the fix or steps handed back that could have run. `LOW` is a message that is not a Conventional Commit, a missing screenshot or a branch left after merge. **Format.** One finding per root cause, citing the step when no file applies: ``` file:line - [rule-id] what is wrong step 3 - [rule-id] what is wrong ``` Then a `Rule | Count | Severity` summary. `Block` when any `HIGH` remains, `Approve` otherwise. Mark every check you could not watch to the end as `Not verified`.
© raphaelsalaja · MIT · raphaelsalaja/skills
Similar skills
All skills for Git and GitHub →ship by other authors comes first.