ds-ship — Claude Code skill for shipping PRs
A Claude Code skill takes a code change through checks and review to a merged pull request. It starts when asked to ship the work, merge once green, or run /ds-ship.
MIT 534 installs ★ 320 updated 2026-10-28
npx skills add aicodeking/deepseek-stack --skill ds-ship -a claude-codeWhat ds-ship does
The skill makes the smallest change that meets the request, verifies the diff, and carries the pull request through merge. It reruns the reported failure after the fix and runs the checks used by CI. For UI or runtime changes, it launches the app and inspects the result. Commands and their output serve as evidence.
It then uses ds-review-loop, ds-pr, and ds-watch-pr to review the change, open the PR, track checks, and handle findings. Merging requires proof for the full diff, green required checks, completed review bots, resolved findings, and a current, mergeable branch. It does not bypass the gate with --admin.
After six fix-and-watch cycles without a passing gate, the skill stops and reports the blocker. It asks before deleting data, touching production, closing a PR, or pushing another branch.
What it helps with
- carry a code change through to a merged PR
- reproduce a failure and verify its fix
- handle review findings and CI failures
- wait for checks before merging a branch
Example prompts for the agent
- Take this change through review and checks, then merge the PR when the gate passes.
- Ship the current work all the way and report the proof for each change.
- Run
/ds-shipon this task and take it through to a merged PR.
How to install ds-ship
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ship -a claude-code2Manually: put the files in place
~/.claude/skills/ds-ship/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ds-ship/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ship -a codex2Manually: put the files in place
.agents/skills/ds-ship/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ship -a cursor2Manually: put the files in place
.cursor/skills/ds-ship/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aicodeking/deepseek-stack skills/ds-ship2Manually: put the files in place
.github/skills/ds-ship/SKILL.md1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ship -a gemini-cli2Platform CLI
gemini skills install https://github.com/aicodeking/deepseek-stack --path skills/ds-shipManually: put the files in place
.devin/skills/ds-ship/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-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 ds-ship
How do I install ds-ship in Claude Code?
Run npx skills add aicodeking/deepseek-stack --skill ds-ship -a claude-code. The skill file is at ~/.claude/skills/ds-ship/SKILL.md.
What does ds-ship do?
It changes the code, verifies the diff, opens a pull request, tracks CI and review, then merges when the merge gate passes. Its final report includes the PR link, merge commit, and proof.
When does ds-ship stop instead of merging?
It stops if it cannot prove the change or pass the merge gate. It also asks before deleting data, touching production, closing a PR, or pushing another branch.
Source text
SKILL.md · MIT
--- name: ds-ship description: "Takes a change all the way from code to a merged pull request without supervision: build it, prove it, review it, file the PR, watch it and merge it. Use when the user says ship it, send it all the way, merge when green, or /ds-ship." --- Own the work from its current state to a merged PR while nobody is watching. Only act this way when the user clearly asked for it. The request grants three things: run the tests and app checks the proof needs without asking first, force-push this task's own branch with `--force-with-lease`, and merge once the gate below passes. It grants nothing else. ## Steps 1. If you are on the default branch, create a new branch. 2. Make the smallest change that meets the goal. Fix the case that was reported, not every case that might exist. 3. Prove every part of the diff. Reproduce the failure, apply the fix, and run the same reproduction again. Run the checks CI runs. For UI or runtime behavior, run the app and look. Paste the command and its output into your notes. 4. Review the change with `ds-review-loop`. Re-prove anything the review changed. 5. Rebase on the latest default branch, then file the PR with `ds-pr`. Add one line that says how you proved it. 6. Watch the PR with `ds-watch-pr`. Fix real findings and CI failures, prove each fix, push, and watch again. 7. Check the merge gate on the latest commit. Merge with the repo's usual method. Never use `--admin` or any other bypass. 8. Report the PR link, merge commit, proof, and every decision you made for the user. Merge gate, all true on the latest head: proof covers the full diff, required checks are green, review bots are finished, each finding is fixed or answered with a reason, no human review asks for changes, and the branch is current and mergeable. ## Stop when - The PR is merged and the report is written. - You cannot prove the change, or the gate cannot pass and you cannot fix it. Ask the user. - The next step deletes data, touches production, closes a PR, or pushes another branch. Ask the user. - Six fix-and-watch cycles pass without a green gate. Stop and report what blocks it. ## Rules - Do not end your turn while checks are pending. Wait with the watcher. - Ask with the harness question tool, not a plain message. Put the PR link, the blocker and your recommended option in the question. - If no question tool exists or nobody answers, leave the PR open and unmerged, and start your final message with the question. - Evidence is output you saw in this session. A claim without output is not proof. - Keep scope fixed. Decline extra work from reviews and list it as follow-ups.
© aicodeking · MIT · aicodeking/deepseek-stack