メニュー
Phase 4 of dual-haul. Fires once the /goal condition is met (the goal auto-clears) or the round cap is hit. Reports goal-vs-achieved with the final check numbers, which racer won each round and why, the net diff that was kept, and what's still open. Writes .dualhaul/SUMMARY.md. Use after dual-loop concludes a dual-haul run.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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".
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.
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.
Fold one lesson into one existing skill, behind a confirmation gate.
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).
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.
| name | dual-report |
| description | Phase 4 of dual-haul. Fires once the /goal condition is met (the goal auto-clears) or the round cap is hit. Reports goal-vs-achieved with the final check numbers, which racer won each round and why, the net diff that was kept, and what's still open. Writes .dualhaul/SUMMARY.md. Use after dual-loop concludes a dual-haul run. |
Phase 4 of dual-haul. Runs when iteration ends — either the goal cleared
(condition met) or the round cap was reached. Produces .dualhaul/SUMMARY.md
and a concise chat recap. This is also the source for the PR body in dual-ship.
Read STATE.md (round log), every R<N>.md, and the current main tree. Then
write .dualhaul/SUMMARY.md (template in
../dual-haul/reference/file-formats.md) covering:
/goal condition and whether it was met. If partial (cap hit), give the final check numbers and how far short.git diff <BASE>..HEAD --stat), and the before→after on the success signal.Before writing "goal achieved", actually run the stated check on the main tree and paste the output. Evidence before assertion — a summary that overstates the result is worse than one that honestly reports a partial win.
Show the user the recap (goal-vs-achieved + net diff stat + correctness line),
then advance PHASE: cleanup and hand to dual-ship:
Goal met (or: cap reached, partial). Summary in
.dualhaul/SUMMARY.md. Next:dual-shipto commit on a branch and open a PR — I'll show you the PR body and branch first.
Leave the worktrees alone — dual-ship tears them down as part of finishing.