harness:finishing-a-development-branch

What problem does it solve?

Finishing a feature safely is hard because teams must confirm correctness (tests), choose the right integration path (merge, PR, keep, or discard), and ensure required operational handoffs (feature status, progress sync, and archive) happen before completion.

Core Features & Use Cases

• Test-gated completion: Verifies the project’s test suite before offering any integration or cleanup choices.
• Environment-aware integration menu: Detects repo/worktree state (normal, worktree, detached HEAD) and presents exactly the allowed merge/PR/keep/discard options for that scenario.
• Operational integrations on completion: Updates features.json status to done, mirrors outcomes into claude-progress.json, and requires invoking harness:archive before reporting completion.
• Deployment-surface safeguard: Prompts the user about harness:canary when the change touches CI/CD or deployment-related surfaces, without auto-invoking it.

Quick Start

Use this skill when your implementation is complete and tests are passing, by telling the agent: "Complete this feature using harness:finishing-a-development-branch and propose the correct next integration option."