使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-ready開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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-shipand 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-shipmerge 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.
