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.
Done when
The workflow is done when the branch state and options are reported, any selected action has been performed and read back, and cleanup happened only where it was authorized and verified. Stop and ask before any option the user has not selected or already authorized.
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
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Report Branch state, Scope reconciliation, Validation, Remote and review state, Options, Selected authority, and Final readback.
Example
Synthetic example; not an observed client result.
Input: The patch is tested locally; no push or cleanup was requested.
Output: The branch is ready for a delivery decision. Report its revision and checks; retain it until the user chooses the next authorized state.
1---2name: finish-branch3description: "Assesses next steps for a finished branch when explicitly asked to wrap up development; presents PR, retention, or cleanup options without assuming merge or deletion authority."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/finish-branch7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "explicit"11 provenance: "original"12 risk_class: "external-write"13---1415# Finish Development Branch1617Make the branch state and available integration choices explicit before any irreversible action.1819## Workflow20211. Verify repository identity, remote, branch, base, exact head, worktree status, commits, and diff.222. Reconcile the requested scope, implemented behavior, tests, review state, and unresolved risks.233. Check whether the remote branch or pull request already exists and whether its head matches local state.244. Present distinct options: retain locally, push, open or update a PR, request review, merge through an authorized method, or clean up after verified integration.255. State the consequences and prerequisites of each option.266. Perform only the option the user explicitly selects or has already authorized.277. Read back remote and merge state after any authorized external action.288. Remove worktrees or branches only after verifying integration, ownership, and absence of uncommitted work.2930## Done when3132The workflow is done when the branch state and options are reported, any selected action has been performed and read back, and cleanup happened only where it was authorized and verified. Stop and ask before any option the user has not selected or already authorized.3334## Boundaries3536- Explicit invocation does not automatically authorize push, PR creation, merge, deletion, or deployment.37- Do not confuse a mergeable branch with an approved or merged branch.38- Never discard unrelated or uncommitted work during cleanup.3940## Output4142Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.4344Report `Branch state`, `Scope reconciliation`, `Validation`, `Remote and review state`, `Options`, `Selected authority`, and `Final readback`.4546## Example4748Synthetic example; not an observed client result.4950Input: The patch is tested locally; no push or cleanup was requested.5152Output: The branch is ready for a delivery decision. Report its revision and checks; retain it until the user chooses the next authorized state.