mcpField
D
ds-ready

ds-ready

github.com/aicodekingDevelopment150268 installsUpdated 6d ago
Repository

About ds-ready

ds-ready is a skill for completing ds-ship’s workflow without merging the pull request. It leaves the PR open and reports whether it is ready, awaiting approval, or blocked, with evidence from checks and merge status.

Key features

  1. 01Following ds-ship steps through PR monitoring
  2. 02Preventing automatic merge before pushes
  3. 03Rechecking behavior after fixes
  4. 04Inspecting live PR status and checks
  5. 05Reporting a merge-gate verdict with evidence

Use cases

  1. 01Preparing a change for human approval
  2. 02Leaving a verified PR open and unmerged
  3. 03Identifying blockers to a PR merge gate

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-ready

After installing, type/ds-readyin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported