finishing-a-development-branch

To safely finalize a git development branch, this Skill runs your project's test suite to verify code stability and ensures all prior verification gates are met before presenting clear integration options like merging or creating a pull request.

The best way to merge completed code changes or create a pull request is to use a structured integration workflow that provides clear choices for merging locally, pushing for PR creation, keeping the branch, or discarding work entirely.

To clean up temporary worktrees and project state after code integration, this Skill manages the final stages of your work by handling robust confirmation and cleanup procedures once your chosen integration path is complete.

Yes, you can discard work and handle branch cleanup if tests fail, because this Skill verifies code integrity through tests as a mandatory gate before proceeding with any merge, pull request, or branch deletion actions.

Yes, this branch integration process preserves knowledge discovered during development by capturing and promoting important findings, ensuring valuable insights are stored before any project state cleanup or worktree removal occurs.

If prior verification steps are not met when finishing a branch, the Skill halts the code integration process to prevent unstable merges, ensuring your project's test suite passes and code integrity is fully verified before proceeding.