finishing-a-development-branch

Automating git branch cleanup requires verifying tests, executing merges, and removing branches safely. This skill standardizes that workflow by applying automated safety checks before integration actions and repository hygiene tasks.

A safe branch merge workflow mandates passing all tests before integration. This skill enforces automated test verification using standard runners, ensuring code integrity before allowing any destructive git actions or branch removal.

Yes, the branch finishing workflow supports git worktrees. It features environment-aware detection to automatically determine whether you are in a standard repository or a managed worktree, applying the correct cleanup strategy accordingly.

No specific test runner is mandated; the skill requires standard test runners to verify code integrity. It integrates with your existing software engineering workflow to ensure tests pass before allowing any merge execution.

Merging a branch triggers a documentation lifecycle transition. Upon successful merge, this skill automatically handles archiving active specs and plans into ADRs, maintaining repository documentation hygiene alongside code integration.

Discarding a branch safely involves automated test verification and environment-aware cleanup. This skill presents appropriate options for removal, ensuring worktree integrity and repository hygiene are maintained when abandoning feature branches.