finishing-a-development-branch

To verify a completed git branch before merging, run relevant tests and inspect branch context to confirm the work is ready. This verification step ensures tests pass and workflow artifacts are classified before making integration decisions.

The best way to close out a development branch is to follow a gated process of explicit verification, context inspection, and artifact triage. This structured process prevents premature integration and avoids destructive cleanup by presenting bounded next actions.

Manage workflow artifacts when finishing a development branch by inspecting branch context and classifying documents for retention, extraction, or deletion. Artifact triage ensures supporting files are properly handled before closeout.

Yes, you can use this git workflow for packet-managed branches. The closeout verification process applies to both packet-managed and standard git workflows when confirming tests and classifying workflow artifacts.

Avoid premature integration when finishing a branch because it risks merging unverified code or losing important workflow artifacts. Gated decision prompts ensure closeout steps remain deliberate and reversible.

After verification passes, you should choose to merge, create a pull request, keep the branch, or discard it. The Skill presents a bounded set of next actions to keep the closeout decision deliberate.