finishing-a-development-branch

To verify tests before merging a Git branch, the Skill runs your specified test command and ensures the suite passes. It targets Git workflows to enforce safe, auditable steps before integrating any development work.

When finishing a development branch, your options are merging locally, pushing for a pull request, keeping the branch as-is, or discarding the work. The Skill enforces these four fixed completion choices.

To automate pull request creation after passing tests, the Skill verifies your test suite and then presents an option to push and create a PR. It automates the finalization of feature work safely.

No specific test framework is required for Git branch finalization. You must specify the test command used by your project, allowing the Skill to verify tests regardless of the underlying testing framework.

Yes, you can discard a Git branch safely after development work. The Skill presents an explicit option to discard the work and performs post-completion cleanup to maintain a clean workspace and history.

Git branch cleanup after merging a feature works by performing post-completion cleanup automatically. The Skill finalizes your chosen integration path and maintains a clean workspace and auditable history.