finishing-a-development-branch

To finalize a git development branch, the skill verifies tests pass, detects the repository environment state, presents structured merge or pull request options, and cleans up the workspace after completion.

The best way to merge a completed development branch is using a structured workflow that first ensures all tests pass, then detects the current worktree status to guide you through integrating the code and cleaning up the repository.

Verifying tests before creating a pull request is handled automatically by the skill, which checks that all tests pass successfully before presenting any options to merge or submit your development branch.

Yes, you need working knowledge of Git and familiarity with branching strategies to effectively use this skill for managing repository branch completion and understanding the presented integration options.

Yes, you can discard a development branch instead of merging it, as the skill provides a structured set of options that includes discarding branches, creating a pull request, or merging directly based on your repository state.

Detecting the environment state is required during branch finalization to adjust the workflow based on the current repository conditions, such as identifying the branch type and worktree status before presenting integration actions.