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 职业分类
| 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.
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.