メニュー
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.
Use when resuming work in this repo after a pause or starting a fresh session on in-flight changes. Reconstruct the current state, open risks, relevant files, completed verification, and next actions.
| name | dr-finish-and-verify |
| version | 2026-03-31.1 |
| description | Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers. |
This skill replaces the old deploy and version-control carryovers.
Load dr-repo-reference first for shared verification and runtime checks.
Use it to:
This repo does not use jj as a first-class workflow. Use normal git commands unless the user explicitly asks for something else.
If the user is trying to ship or declare the repo production-ready, hand off to
dr-production-readiness before making that claim.
If this skill is being used inside dr-autonomous-iteration and the overall user goal is still in progress:
active-slice.md if one existsDo not declare the slice done until:
Use the component verification matrix from dr-repo-reference.
Review state first:
git status --short
git diff --stat
git diff
Commit:
git add path/to/file.go path/to/file_test.go
git commit -m "type: short description"
Push:
git push origin HEAD
When a local deployment-style check is needed:
docker-compose up -d
docker-compose ps
docker-compose logs --tail=200
docker-compose up aloneGOOS=windows for dr-agent/