dual-ship

Stars8

Forks1

UpdatedJuly 1, 2026 at 19:46

Phase 5 of dual-haul — the finishing move. Commits the kept improvement on a feature branch, opens a PR (body drawn from .dualhaul/SUMMARY.md), and tears down the dual-haul worktrees and state. Always confirms the branch name and PR body with the user before pushing. Use as the last phase of a dual-haul run, after dual-report.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

ccomkhj

ccomkhj/skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	dual-ship
description	Phase 5 of dual-haul — the finishing move. Commits the kept improvement on a feature branch, opens a PR (body drawn from .dualhaul/SUMMARY.md), and tears down the dual-haul worktrees and state. Always confirms the branch name and PR body with the user before pushing. Use as the last phase of a dual-haul run, after dual-report.

dual-ship

Phase 5 of dual-haul. Ships the kept improvement and cleans up the machinery. This is an outward-facing action (a PR) — confirm with the user before pushing anything.

Preconditions

dual-report has written .dualhaul/SUMMARY.md.
The kept changes are committed on the main working branch (dual-loop merged each winner). If there are uncommitted leftovers, show git status and ask before proceeding.

Steps

Tear down racer worktrees first. goal_teardown (no round arg removes both wt-claude/wt-codex and prunes); then git branch --list 'dualhaul/*' and delete any leftover temp branches. The PR must contain only the kept improvement, not race scaffolding.
Branch. If the work landed on main/master, create a feature branch (e.g. dualhaul/<short-topic>) and move the commits there — never open a PR from the default branch. If already on a feature branch, use it.
Confirm — the gate. Show the user: the branch name, the commit list (git log <base>..HEAD --oneline), and the proposed PR title + body (drawn from SUMMARY.md: goal, what was achieved, net diff, correctness, follow-ups). Set STATUS: WAITING-USER: confirm-pr. Wait for an explicit yes.
Push + PR. On confirmation: git push -u origin <branch>, then gh pr create --title "…" --body "…" (body from SUMMARY.md). Report the PR URL.
Finish. Set STATUS: DONE, PHASE: cleanup in STATE.md. Ask the user whether to delete .dualhaul/ now or keep it for reference (it's gitignored either way). If they ran /goal and it's somehow still active, remind them it auto-cleared on success, or to /goal clear.

PR body shape

Pull straight from SUMMARY.md. End the body with the standard trailer:

🤖 Generated with [Claude Code](https://claude.com/claude-code)

And the commits (if you author them here) end with:

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Don't

Don't push or open a PR before the user confirms — it's outward-facing and hard to reverse.
Don't include .dualhaul/ or the dualhaul/r<N>-* branches in the PR. They're transient.
Don't claim the PR is open until gh pr create returns a URL — paste it.

More from this repository

same repository

agents-md-improver

ccomkhj/skills

Audit and improve AGENTS.md files in repositories, keeping CLAUDE.md as a one-line @AGENTS.md reference so the same project memory works across tools (Claude Code, Codex, Gemini CLI, …). Use when user asks to check, audit, update, improve, or fix AGENTS.md (or CLAUDE.md) files. Scans for all such files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "AGENTS.md maintenance" or cross-tool "project memory optimization".

2026-07-188

inspect-skill-flow

ccomkhj/skills

Graph a skill's flow — steps, artifacts, invocations — render it with draw-graphology, and report checkable weak links — each verified by two independent subagents — as a handoff file of lessons for improve-skills.

2026-07-138

slack-comm

ccomkhj/skills

Summarize the CURRENT Claude session's work into a very concise 3P (Progress/Plans/Problems) Slack status report, draft it to the user for review, then place it as a native Slack draft for a final look before they send. User-invoked mid-session (`/slack-comm`) when you need to report what you just did in a tight, matter-of-fact format. Not for org-scale newsletters or pulling other people's updates.

2026-07-088

improve-skills

ccomkhj/skills

Fold one lesson into one existing skill, behind a confirmation gate.

2026-07-048

lunch-clean-loop

ccomkhj/skills

Unattended cleanup loop — scan the codebase for readability debt and run up to N targets (default 5) through a cleaner/reviewer/tester trio; verified cleanups land as per-target refactor commits on a clean-loop/<date> branch. Not a performance tool (pair-ratchet) and not for polishing just-written code (simplify-python).

2026-07-048

draw-graphology

ccomkhj/skills

Create data-driven network graph visualizations with graphology + sigma.js. Use when the user wants to visualize a network, dependency graph, knowledge graph, call graph, org/relationship map, communities/clusters, or any node-edge dataset too large to place by hand.

2026-07-038

name	dual-ship
description	Phase 5 of dual-haul — the finishing move. Commits the kept improvement on a feature branch, opens a PR (body drawn from .dualhaul/SUMMARY.md), and tears down the dual-haul worktrees and state. Always confirms the branch name and PR body with the user before pushing. Use as the last phase of a dual-haul run, after dual-report.

dual-ship

Phase 5 of dual-haul. Ships the kept improvement and cleans up the machinery. This is an outward-facing action (a PR) — confirm with the user before pushing anything.

Preconditions

dual-report has written .dualhaul/SUMMARY.md.
The kept changes are committed on the main working branch (dual-loop merged each winner). If there are uncommitted leftovers, show git status and ask before proceeding.

Steps

Tear down racer worktrees first. goal_teardown (no round arg removes both wt-claude/wt-codex and prunes); then git branch --list 'dualhaul/*' and delete any leftover temp branches. The PR must contain only the kept improvement, not race scaffolding.
Branch. If the work landed on main/master, create a feature branch (e.g. dualhaul/<short-topic>) and move the commits there — never open a PR from the default branch. If already on a feature branch, use it.
Confirm — the gate. Show the user: the branch name, the commit list (git log <base>..HEAD --oneline), and the proposed PR title + body (drawn from SUMMARY.md: goal, what was achieved, net diff, correctness, follow-ups). Set STATUS: WAITING-USER: confirm-pr. Wait for an explicit yes.
Push + PR. On confirmation: git push -u origin <branch>, then gh pr create --title "…" --body "…" (body from SUMMARY.md). Report the PR URL.
Finish. Set STATUS: DONE, PHASE: cleanup in STATE.md. Ask the user whether to delete .dualhaul/ now or keep it for reference (it's gitignored either way). If they ran /goal and it's somehow still active, remind them it auto-cleared on success, or to /goal clear.

PR body shape

Pull straight from SUMMARY.md. End the body with the standard trailer:

🤖 Generated with [Claude Code](https://claude.com/claude-code)

And the commits (if you author them here) end with:

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Don't

Don't push or open a PR before the user confirms — it's outward-facing and hard to reverse.
Don't include .dualhaul/ or the dualhaul/r<N>-* branches in the PR. They're transient.
Don't claim the PR is open until gh pr create returns a URL — paste it.