ds-ready — Claude Code skill: what it does, how to install
ds-ready is a Claude Code skill that automates the delivery workflow through opening a pull request, then stops before merging.
MIT 534 installs ★ 320 updated 2026-10-28
npx skills add aicodeking/deepseek-stack --skill ds-ready -a claude-codeWhat ds-ready does
The skill follows the ds-ship steps for branching, changing, testing and reviewing, but leaves the pull request open for human approval instead of merging. Before pushing, the agent disables auto-merge and checks merge queues. If the gate does not pass after six fix cycles, the agent reports a block.
The agent uses the same test permissions as ds-ship, including committing, pushing, rebasing and --force-with-lease. Merging, turning on auto-merge, joining merge queues and pushing to the default branch are strictly forbidden.
What it helps with
- prepare a pull request without merging it automatically
- run tests and reviews before human merge
- stop delivery right before branch integration
- hand over a ready-to-merge pull request
Example prompts for the agent
- Get it ready to merge
- Make this branch mergeable
- Stop before merge
How to install ds-ready
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ready -a claude-code2Manually: put the files in place
~/.claude/skills/ds-ready/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ds-ready/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ready -a codex2Manually: put the files in place
.agents/skills/ds-ready/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ready -a cursor2Manually: put the files in place
.cursor/skills/ds-ready/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aicodeking/deepseek-stack skills/ds-ready2Manually: put the files in place
.github/skills/ds-ready/SKILL.md1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ready -a gemini-cli2Platform CLI
gemini skills install https://github.com/aicodeking/deepseek-stack --path skills/ds-readyManually: put the files in place
.devin/skills/ds-ready/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-ready -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-ready
How to install ds-ready in Claude Code?
Run npx skills add aicodeking/deepseek-stack --skill ds-ready -a claude-code in your terminal and check ~/.claude/skills/ds-ready/SKILL.md.
What does ds-ready do?
It runs the ds-ship workflow up to the pull request stage and stops with an open, unmerged PR.
What are the restrictions in ds-ready?
The agent is never allowed to merge pull requests, enable auto-merge, join merge queues or push to the default branch.
Source text
SKILL.md · MIT
--- name: ds-ready description: "Runs the full ds-ship workflow but stops with the pull request ready for a human to merge, and never merges. Use when the user says get it ready, make it mergeable, stop before merge, or /ds-ready." --- Do all of `ds-ship` except the merge. Hand the user an open PR that passes the merge gate. The request grants the same test permission as `ds-ship`, and you may commit, push, rebase and `--force-with-lease` this task's branch. You may not merge. ## Steps 1. Read `ds-ship` and follow its steps 1 to 6: branch, change, prove, review, file, watch. 2. Before the first push, turn off auto-merge and take the PR out of any merge queue. Check again before each push. If you cannot stop automatic merging, report that before you continue. 3. After the last fix, re-prove any behavior change and any non-trivial conflict resolution. 4. Fetch the base branch. Read the live PR: head SHA, base, checks, reviews, mergeable state. Confirm it is open and not a draft. 5. Apply the `ds-ship` merge gate and pick one verdict: - **Ready**: the gate passes. Leave the PR open. - **Waiting on approval**: only a required human approval is missing. Confirm that this is the real blocker. - **Blocked**: say what stops it, what you tried and what is needed. 6. Report the PR link, final head SHA, verdict, proof, review outcome and remaining risks. State that the PR is open and unmerged. ## Stop when - You reach one of the three verdicts and the report is written. - Someone else merged the PR. Report that. - Six fix-and-watch cycles pass without a green gate. Report Blocked. ## Rules - Never merge, turn on auto-merge, join a merge queue or push to the default branch. - Do not ask another agent to do any of those things for you. - Show evidence for the verdict: the check list and mergeable state you read.
© aicodeking · MIT · aicodeking/deepseek-stack