finishing-a-development-branch

To finish a git feature branch after tests pass, this skill identifies your base branch and presents four explicit options: local merge, PR creation, keep the branch, or discard the work.

Options for merging a completed development branch include merging locally, pushing to create a pull request, keeping the branch as-is, or discarding the work entirely with optional cleanup.

Yes, you can automate git branch cleanup when finalizing a feature because the skill performs optional cleanup after you select your preferred merge, pull request, or discard action.

Yes, this git workflow skill requires passing tests before merging because it applies guardrails around test results and only activates when your repository tests are passing.

The best way to manage pull request creation from a feature branch is using a structured workflow that determines the base branch first, then offers explicit push and PR creation steps.

You need to identify a base branch before merging a git feature because the skill requires a known base branch to properly enumerate merge actions and perform optional cleanup.