Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aicodeking/deepseek-stack --skill ds-ready -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/ds-ready/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ds-ready/

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

Similar skills

All skills for Git and GitHub →

From the same set29

The whole set →
ds-best-of-n The ds-best-of-n Claude Code skill creates several independent versions of a task and combines the strongest result with selected parts from the others. It runs for substantial work where a single attempt may take the wrong direction. CX Codex +1 539installs ds-swarm Claude Code skill splits broad tasks across parallel workers and merges their verified outputs into a single report. Triggers on /ds-swarm during audits or multi-branch races. CX Codex +1 537installs ds-watch-pr ds-watch-pr is a Claude Code skill that follows a pull request through CI and review, fixes real findings, and stops when it is ready, merged, or blocked. CX Codex +1 536installs ds-adopt ds-adopt — a Claude Code skill takes over an existing PR, branch, or agent thread and completes its original goal. It activates when asked to adopt or finish someone else’s work. CX Codex +1 534installs ds-revive The ds-revive Claude Code skill checks whether an old PR still fits the current code. When asked to refresh or revive one, it recommends a rebase, a rewrite, or closure. CX Codex +1 534installs ds-pr ds-pr — a skill for Claude Code and other platforms that files a concise pull request for the current branch when asked to open a PR. CX Codex +1 534installs ds-ship 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. CX Codex +1 534installs ds-pr-comments The ds-pr-comments Claude Code skill formats and posts agent-written GitHub PR comments. It runs for PR comments, review replies, and dismissal reasons. CX Codex +1 531installs

Project sponsors

Companies that keep this analytics open