Finishing a Development Branch closes out completed work. It runs the full test suite first and stops on failures. When the suite is green it works out whether you are in a normal repository, a named-branch worktree or a detached HEAD, shows the options that apply, and carries out the one you choose.
What You Get
- A green-suite gate before any option is shown
- A menu matched to the git state, with three options normally and two on a detached HEAD
- Merge, push and pull request, or keep, run with the right git commands
- Worktree cleanup that asks you before it forces anything
Common Use Cases
- Wrapping up a feature branch after the last task passes
- Opening a pull request from a worktree
- Removing a worktree after a local merge
What Makes It Unique
It compares the git directory with the common git directory to tell worktrees from normal repositories, and adjusts the menu and cleanup to match. Cleanup removes only worktrees under .worktrees or worktrees, the ones the skill family created, and it asks before any forced removal. Discarding work needs the word discard typed back.
Under The Hood
Instructions with shell snippets. The agent runs your test command and git commands: rev-parse to detect the worktree state, checkout, pull and merge, push with upstream tracking, branch delete, and worktree remove and prune. Pull request creation uses the forge’s command-line tool when one is available. It writes no files and calls only your git remotes.