finishing-a-development-branch

Merging a Git branch after tests pass involves running your project's test suite, computing the base branch, and selecting a merge option. This Skill automates that workflow by validating tests first, then presenting merge, PR, preserve, or discard options to integrate your work into the main codebase.

Finish a development branch by running tests, confirming they pass, then choosing to push a PR for code review or merge locally. This Skill guides you through validation and presents exactly four integration paths—including PR creation—so feedback is addressed before merging into main.

Yes. This Skill automates test execution across npm, pytest, go test, and cargo test frameworks, then handles branch cleanup based on your chosen workflow. It runs the full test suite, validates the base branch, and cleans up the worktree after merging, pushing, preserving, or discarding.

This Skill standardizes the final integration stage by validating tests and presenting merge options; it facilitates conflict resolution as part of the merge operation. If conflicts arise during merge, the workflow helps you address them before the branch is fully integrated.

After you finish development, your branch is cleaned up based on the option you select: merged into main, pushed as a PR, preserved for later, or discarded. This Skill ensures the worktree is cleaned accordingly so your repository stays organized.

Yes. This Skill applies across Git branches and worktrees, so you can finish development work regardless of whether you're using standard branches or worktrees. It handles cleanup for both setups.