finishing-a-development-branch
Use when a real branch, integration, or discard decision needs an authorized closeout.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when a real branch, integration, or discard decision needs an authorized closeout.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation.
Consult before delegating implementation when an approved plan benefits from worker context isolation and durable coordination.
Consult before attempting a fix when root cause or behavior is unclear, failures repeat, components interact, or guessing would be unsafe.
Consult before implementing an observable behavior change when a meaningful automated test seam exists; use proportional red-green evidence.
Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow execution.
Consult before making a substantive completion claim; require current trustworthy evidence and semantic acceptance.
| name | finishing-a-development-branch |
| description | Use when a real branch, integration, or discard decision needs an authorized closeout. |
Use this skill only for a real branch, integration, or discard decision with authority to act. Inspect current repository policy, branch/worktree state, relevant tests, and user preference first.
Present the applicable options: keep the diff, use native controls, review, merge, push, or discard. Do not fix the option count. Push, merge, PR creation, or deletion needs authority; never force-push or perform an unauthorized push.
Discard is destructive: show affected work and obtain explicit confirmation before deleting it. Preserve harness-owned workspaces unless ownership and cleanup policy are clear.