finishing-a-development-branch

To finalize a git feature branch after tests pass, this skill presents a structured four-option decision flow for merging locally, creating a pull request, keeping the branch, or discarding work.

The best way to clean up git branches after merging is using safe cleanup guidance, which provides explicit steps to safely delete or preserve branches and worktrees according to your workflow needs.

A development branch workflow handles pull requests and local merges by offering a deterministic post-work decision flow, allowing you to choose between creating a remote PR or executing a local merge.

Yes, you can discard git branch work instead of merging it. The workflow explicitly includes an option to discard work, allowing you to cleanly conclude development without integration if needed.

Yes, you need passing tests before merging a development branch. The workflow requires tests to pass and identification of a base branch before presenting integration or cleanup options.