Finish Development Branch
Make the branch state and available integration choices explicit before any irreversible action.
Workflow
- Verify repository identity, remote, branch, base, exact head, worktree status, commits, and diff.
- Reconcile the requested scope, implemented behavior, tests, review state, and unresolved risks.
- Check whether the remote branch or pull request already exists and whether its head matches local state.
- Present distinct options: retain locally, push, open or update a PR, request review, merge through an authorized method, or clean up after verified integration.
- State the consequences and prerequisites of each option.
- Perform only the option the user explicitly selects or has already authorized.
- Read back remote and merge state after any authorized external action.
- Remove worktrees or branches only after verifying integration, ownership, and absence of uncommitted work.
Boundaries
- Explicit invocation does not automatically authorize push, PR creation, merge, deletion, or deployment.
- Do not confuse a mergeable branch with an approved or merged branch.
- Never discard unrelated or uncommitted work during cleanup.
Output
Report Branch state, Scope reconciliation, Validation, Remote and review state, Options, Selected authority, and Final readback.
1---2name: finish-development-branch-33description: Reconcile a development branch and present evidence-based options for pull request, merge, retention, or cleanup. Invoke explicitly when implementation is complete enough to decide the branch's next state without assuming push, merge, deletion, or abandonment authority.4license: MIT5---67# Finish Development Branch89Make the branch state and available integration choices explicit before any irreversible action.1011## Workflow12131. Verify repository identity, remote, branch, base, exact head, worktree status, commits, and diff.142. Reconcile the requested scope, implemented behavior, tests, review state, and unresolved risks.153. Check whether the remote branch or pull request already exists and whether its head matches local state.164. Present distinct options: retain locally, push, open or update a PR, request review, merge through an authorized method, or clean up after verified integration.175. State the consequences and prerequisites of each option.186. Perform only the option the user explicitly selects or has already authorized.197. Read back remote and merge state after any authorized external action.208. Remove worktrees or branches only after verifying integration, ownership, and absence of uncommitted work.2122## Boundaries2324- Explicit invocation does not automatically authorize push, PR creation, merge, deletion, or deployment.25- Do not confuse a mergeable branch with an approved or merged branch.26- Never discard unrelated or uncommitted work during cleanup.2728## Output2930Report `Branch state`, `Scope reconciliation`, `Validation`, `Remote and review state`, `Options`, `Selected authority`, and `Final readback`.
JovaniPink