What problem does it solve?
This Skill eliminates the guesswork and risk of errors when completing work on a Git development branch, preventing broken merges, accidental work loss, and messy repository state from inconsistent cleanup practices.
Core Features & Use Cases
- Test Verification: Automatically checks that all project tests pass before allowing any branch completion actions, preventing broken code from being merged or pushed.
- Environment-Aware Workflows: Detects if you're working in a normal repository, a named worktree, or a detached HEAD state to present only the relevant, safe options for your setup.
- Safe Cleanup & Guardrails: Handles worktree cleanup only for workspaces you own, requires explicit typed confirmation before permanently discarding any work, and avoids modifying harness-managed workspaces to prevent repository corruption.
- Use Case: A developer who just finished implementing a new patient billing feature in a feature branch can use this Skill to safely merge their tested work to the main branch, or push it as a PR for team review, without risking broken code or lost work.
Quick Start
Use the finishing-a-development-branch skill to safely complete your current feature branch after verifying all tests pass, and choose to merge it locally, push it as a pull request, keep it for later work, or discard it permanently.