finishing-a-development-branch

Merging a finished development branch requires test verification first, then choosing between local merge, pull request, keeping the branch, or discarding it. This Skill enforces passing tests before presenting four structured integration options with exact commands and cleanup steps for each path.

Branch cleanup depends on your chosen integration workflow. After tests pass, this Skill provides safe cleanup procedures tailored to each option: local merge, PR creation, branch retention, or deletion, with automatic worktree management.

After implementing features and running all tests successfully, this Skill presents exactly four clear choices: merge locally to base branch, push a PR for review, keep the branch active, or discard with confirmation, helping you pick the right path for your workflow.

Test verification before branch integration catches errors early and prevents broken code from reaching production or shared branches. This Skill enforces passing tests as a prerequisite, ensuring code quality before presenting integration options.

Yes, this Skill includes base-branch detection that identifies the target branch for integration, eliminating manual configuration and reducing errors when merging or creating pull requests from development work.

If tests fail, this Skill does not present integration options. You must fix failing tests first and re-run verification before the workflow allows you to proceed with any merge, PR, or cleanup action.