Stats
Actions
Tags
From bp
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
How this skill is triggered — by the user, by Claude, or both
Slash command
/bp:finishing-a-development-branchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<skill>
1. Merge locally: checkout base → pull → merge feature branch → verify tests on merged result → delete feature branch.
2. Push and create PR: push branch with -u → gh pr create with Summary + Test Plan.
3. Keep as-is: Report branch name and worktree path. Don't cleanup.
4. Discard: Confirm first (show branch, commits, worktree path). Require typed "discard". Then: checkout base → force-delete feature branch → remove worktree.
Never proceed with failing tests. Never merge without verifying tests on result. Never delete work without typed confirmation. Never force-push without explicit request.Called by: bp:subagent-driven-development (after all tasks), bp:executing-plans (after all batches). Pairs with: bp:using-git-worktrees (cleans up worktree created by that skill).
npx claudepluginhub brandonfla/bearpaws --plugin bpCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.