finishing-a-development-branch

Test verification runs your project's test suite automatically to ensure all changes are stable before integration. This Skill executes the full test suite and detects pass/fail status, preventing untested code from merging into your base branch.

When tests pass, this Skill presents four structured integration paths: merge locally into your base branch, push and create a Pull Request via gh CLI, keep the branch as-is for later, or discard the work entirely. You select the option that fits your workflow.

After choosing your merge path, the Skill handles optional cleanup of your worktree and branch automatically. This prevents dangling branches and orphaned worktrees that clutter your git repository.

This Skill detects your base branch automatically and works with standard git workflows. It requires git and gh CLI as dependencies, supporting common integration patterns across different project structures and team setups.

If your test suite fails, the Skill halts before presenting merge options, preventing broken code from integrating. You must resolve test failures before proceeding to merge, ensuring only validated changes reach your base branch.

No—this Skill automatically detects your base branch as part of its integration logic. Base-branch detection eliminates manual specification, reducing the risk of merging into the wrong target branch.