finishing-a-development-branch

To finalize a development branch, this Skill automatically verifies that your project tests pass before proceeding. Once tests pass, it determines the base branch and presents structured options to merge locally, create a pull request, or discard the work.

The best way to manage worktree cleanup is by using an integration strategy that handles cleanup or preservation automatically. This Skill manages worktree cleanup based on your chosen branch integration method, whether you merge or create a pull request.

To create a pull request or merge code locally after finishing development, this Skill guides you through structured options for code integration. It ensures tests pass first, then executes the necessary Git commands for your chosen path.

Yes, you can discard your current development work if tests fail or the feature is no longer needed. This Skill presents discarding the work as a structured option alongside merging or creating a pull request.

Yes, this branch management workflow determines the correct base branch automatically. It identifies the appropriate base branch before presenting structured options for merging, pull request creation, or discarding your completed development work.

A limitation of automating code integration is that this Skill requires project tests to pass before allowing you to proceed with any branch management options. You cannot merge, create a pull request, or discard work until test verification is complete.