ワンクリックで
pr
Ship a done goal as one PR of cherry-picked commits. Use when asked to open a PR for /sddx:run goals.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Ship a done goal as one PR of cherry-picked commits. Use when asked to open a PR for /sddx:run goals.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Turn a development goal into a dense sddx spec — binary success criteria, a mandatory oracle, stop rules — and register it as a task. Use when the user wants to plan or spec out a task before executing it.
Flagship sddx flow — decompose a goal into oracle-backed task specs and run them through TDD loops in parallel git worktrees, each ending in a verified, hash-chained receipt. Use for multi-task goals or any task that should run isolated from the current checkout.
Run a single sddx task through the PLAN → RED → GREEN → REFACTOR → VERIFY loop. Use when the user asks to execute one small, well-scoped task with spec-driven TDD.
Execute a task's oracle and, on pass, produce the hash-chained receipt and atomic commit. Use when an sddx task reaches VERIFY or the user asks to verify a task.
Verify the receipt hash chain, commit bindings, and (optionally) commit signatures. Use when the user asks to audit sddx receipts or check the integrity of completed work.
Regenerate .sddx/BOARD.md and show task status across the repo and its worktrees. Use when the user asks for sddx status, the board, or task progress.
| name | pr |
| description | Ship a done goal as one PR of cherry-picked commits. Use when asked to open a PR for /sddx:run goals. |
CLI: "${CLAUDE_PLUGIN_ROOT}/bin/sddx-run" "${CLAUDE_PLUGIN_ROOT}/dist/cli.mjs" (run from the repo root).
Run: ... pr create --goal <goal-id> [--title "<title>"]
This is the sending end of the loop /sddx:run deliberately stops short of:
one goal becomes one PR, built from that goal's already-verified task
commits — never invoked automatically, only when the user asks.
.sddx/goals/<goal-id>.json is
DONE with a passing receipt, re-read fresh at invocation time — no
partial-goal PRs. On refusal it names exactly which task is blocking and
why (wrong phase, no receipt, or missing entirely).gh or glab, from
userConfig.pr_host or detected from the origin remote) and checks it's
authenticated before touching git — a failed preflight leaves nothing to
clean up.sddx/goal-<goal-id> from the
resolved base and cherry-picks each task's single atomic commit onto it,
in task-creation order. A conflict aborts the whole operation — no branch
pushed, no partial PR — and names the task whose commit failed.shipped marker onto every task's own branch and
onto the goal file. This is what later lets sddx cleanup <id> delete a
cherry-picked task branch even though it will never look "merged" by git
ancestry.Print the PR URL, the goal branch name, and the task ids it contains. If the
command refuses, report the exact reason verbatim — don't retry with a
different task set or paper over a blocking task by re-running verify
without a real fix.
task_ids to exclude
a blocking task. If the user wants to ship early, that's a manual PR
outside sddx, not this command.pr create.