aicodekingaicodeking/deepseek-stack/skills/ds-ready/SKILL.md

ds-ready

Skill80 starsChanged 15 days agoMITView on GitHub

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.

In this repository28 other files it gives its agents.
- ds-adoptSkill
- ds-best-of-nSkill
- ds-blast-radiusSkill
- ds-blueprintSkill
- ds-catchupSkill
- ds-context-resetSkill
- ds-design-auditSkill
- ds-designSkill
- ds-explainSkill
- ds-helpSkill
- ds-jurySkill
- ds-ledgerSkill
- ds-lessonsSkill
- ds-modeSkill
- ds-plan-loopSkill
- ds-pr-commentsSkill
- ds-principlesSkill
- ds-prSkill
- ds-review-loopSkill
- ds-reviveSkill
- ds-sharpenSkill
- ds-shipSkill
- ds-swarmSkill
- ds-tddSkill
- ds-unslopSkill
- ds-unstickSkill
- ds-verify-loopSkill
- ds-watch-prSkill

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Very specific:
Do all of ds-ship except the merge.
line 6
Very specific:
Read ds-ship and follow its steps 1 to 6: branch, change, prove, review, file, watch.
line 12
Distinctive:
Before the first push, turn off auto-merge and take the PR out of any merge queue.
line 13
Distinctive:
After the last fix, re-prove any behavior change and any non-trivial conflict resolution.
line 14
Distinctive:
Waiting on approval: only a required human approval is missing.
line 18
Distinctive:
Never merge, turn on auto-merge, join a merge queue or push to the default branch.
line 30
Distinctive:
Do not ask another agent to do any of those things for you.
line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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

Read ds-ship and follow its steps 1 to 6: branch, change, prove, review, file, watch.
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.
After the last fix, re-prove any behavior change and any non-trivial conflict resolution.
Fetch the base branch. Read the live PR: head SHA, base, checks, reviews, mergeable state. Confirm it is open and not a draft.
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.
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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free