finishing-a-development-branch

Guides completion of development branches through structured merge, pull request, or cleanup options.

Updated Jan 28, 2026

Search Tags:#git #pull request #worktree #branch management #merge #test verification #github cli

Ready to run

npx skills add https://github.com/ttphats/project-detedxs26 --skill finishing-a-development-branch-ttphats

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/ttphats/project-detedxs26/tree/main/.augment/skills/superpowers/finishing-a-development-branch
Command: npx skills add https://github.com/ttphats/project-detedxs26 --skill finishing-a-development-branch-ttphats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often merge broken code, forget to run tests, or leave stale branches and worktrees behind. This Skill enforces a disciplined completion workflow so every branch ends in a verified, deliberate state. ## Core Features & Use Cases - Pre-flight verification: Scans changed files for emojis and runs the project's test suite before any merge or PR is allowed. - Structured completion options: Presents exactly four choices—merge locally, push and create a pull request, keep the branch, or discard the work with typed confirmation. - Worktree cleanup: Removes git worktrees only when appropriate, preserving them for PR or keep-as-is flows. - Use Case: After finishing a feature branch with passing tests, use this Skill to verify the diff is clean, create a GitHub pull request via `gh pr create`, and clean up the local worktree. ## Quick Start Use the finishing-a-development-branch skill to verify my tests pass and help me merge this feature branch back into main.

Frequently Asked Questions about finishing-a-development-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely merge a feature branch after development is complete?▼

Verify the test suite passes first, then checkout the base branch, pull latest changes, merge the feature branch, and re-run tests on the merged result. Only delete the feature branch after the merged code passes tests.

How to create a GitHub pull request from the command line?▼

Push the branch with git push -u origin, then run gh pr create with a title and body containing a summary of changes and a test plan checklist. The GitHub CLI must be installed and authenticated.

When should I remove a git worktree after finishing a branch?▼

Remove the worktree only when the branch was merged locally or discarded. Keep the worktree when you created a pull request or chose to keep the branch, since you may still need the working files.

What happens if tests fail before merging a branch?▼

The workflow stops immediately and reports the failing tests. No merge, pull request, or cleanup proceeds until all test failures are fixed, preventing broken code from reaching the base branch.

Can I undo discarding a development branch?▼

No, discarding force-deletes the branch and its commits permanently. That is why the workflow requires typing the exact word 'discard' as confirmation before executing git branch -D.