Complete and merge development branches with test verification

Finishing a Development Branch guides completion of finished work through a fixed sequence: verify tests, present options, execute the chosen option, clean up. It announces itself, then runs the project's test suite (npm test/cargo test/pytest/go test ./...) and refuses to proceed if any test fails, reporting the failure count and blocking merge or PR until it's fixed. It determines the base branch via git merge-base HEAD main or master, checks AGENTS.md and the base branch's actual protection settings, and if pull requests or required checks are enforced, disables the local-merge option and routes through the repository's guarded PR workflow instead. It then presents exactly four options with no extra explanation - merge back to the base branch locally, push and create a Pull Request, keep the branch as-is, or discard the work - trimmed to three, no local merge, on a protected base branch. Discard requires typed confirmation of the exact word "discard" after listing everything that will be deleted. Worktree cleanup (git worktree remove) runs only for the merge and discard options; keeping the branch as-is or opening a PR preserves the worktree.

Use it once all development work on a branch is complete and you need a structured way to land it - after subagent-driven-development's final step, or executing-plans' final step once all batches are done. Never skip test verification to save time, since that's how broken code gets merged or a failing PR gets opened; never offer an open-ended "what next" question instead of the four fixed options; and never force-push without an explicit request. It pairs with using-git-worktrees, cleaning up the worktree that skill created.

Input: a completed feature branch, its test suite, and the repository's base-branch protection state. Output: one of four executed actions - a local merge with a deleted feature branch, a pushed branch with an opened PR via gh pr create with a Summary and Test Plan body, an untouched branch left in place, or a confirmed, permanent branch deletion - each paired with the correct worktree cleanup behavior per the skill's own quick-reference table.

• Git (merge-base, checkout, pull, merge, branch -d/-D, worktree remove)
• GitHub CLI (gh pr create)
• AGENTS.md and maintainer documentation for branch-protection rules
• In agentic-awesome-skills specifically, defers maintainer merges to antigravity-maintainer-batch-release and npm run merge:batch
• Called by subagent-driven-development and executing-plans; pairs with using-git-worktrees

Anyone using an AI agent to land finished development work safely - verifying tests first, respecting branch protection, and never deleting work without explicit typed confirmation.