finishing-a-development-branch

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill finishing-a-development-branch-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill finishing-a-development-branch-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often merge broken code, forget to verify tests, or accidentally delete work. This Skill enforces a safe, structured completion workflow for Git feature branches. ## Core Features & Use Cases - Test Gate: Verifies the project's test suite passes before offering any completion options, blocking merges of failing code. - Structured Options: Presents exactly four choices—merge locally, push and create a PR, keep the branch, or discard—so the next step is never ambiguous. - Safe Cleanup: Requires typed confirmation before discarding work and removes Git worktrees only when appropriate. - Use Case: After finishing a feature on a branch in a Git worktree, use this Skill to run the tests, create a pull request with a summary and test plan via the GitHub CLI, and clean up the worktree. ## Quick Start Use the finishing-a-development-branch skill to verify my tests pass and help me merge or create a PR for this completed feature branch.

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 finish a Git feature branch after development?

First verify the project's test suite passes, then choose between merging locally into the base branch, pushing and creating a pull request, keeping the branch, or discarding it. Never merge or delete work before tests pass.

How do I create a pull request from the command line?

Push the feature 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 opens the PR against the base branch.

When should I remove a Git worktree after merging?

Remove the worktree only after merging locally or discarding the branch, using git worktree remove. Keep the worktree when you created a pull request or chose to keep the branch, since the work may still be needed.

What happens if tests fail before merging a branch?

The process stops immediately and reports the failing tests. You must fix the failures before any merge, pull request, or cleanup option is offered, preventing broken code from reaching the base branch.

How do I avoid accidentally deleting a Git branch?

Require explicit typed confirmation, such as typing 'discard', before force-deleting a branch with git branch -D. Show the branch name, commit list, and worktree path in the confirmation prompt so the user knows exactly what will be lost.