finishing-a-development-branch

To finalize a Git development branch after tests pass, you can choose to merge locally, push and create a pull request, keep the branch as-is, or discard the work entirely. The Skill guides you through selecting and executing one of these structured merge options.

The best way to manage a branch lifecycle after development is to verify test results, generate an Implementation Report, and execute post-merge cleanup. This Skill coordinates the finalization steps to ensure completed changes are safely integrated and old branches are handled properly.

You coordinate test verification before creating a pull request by running the test suite and validating that all tests pass. Once verified, this Skill helps you push the branch and generate the necessary PR documentation to proceed with integration.

Yes, you can discard completed work and clean up a Git branch locally. The Skill presents an option to discard the work and coordinates the cleanup steps required to remove the branch from your Git workflow after tests pass.

Yes, this workflow supports generating an Implementation Report before merging. After your tests pass, the Skill produces an Implementation Report template to document the changes before you proceed with your chosen merge or pull request option.