finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Before you install
- Last update
- Files in folder
- 1
- Scripts
- No script files found
- SKILL.md size
- 7.6 KB (about 1,945 tokens of context each time it loads)
- License
- MIT
- Source on GitHub
- obra/superpowers
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add obra/superpowers@finishing-a-development-branchRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add obra/superpowers@finishing-a-development-branch --agent claude-code -y- Project install writes to
.claude/skills/finishing-a-development-branch- Global install writes to
~/.claude/skills/finishing-a-development-branch
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /finishing-a-development-branch.
What it does
Finishing a Development Branch Overview Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up. Announce at start: "I'm using the finishing-a-development-branch skill to complete this work." Step 1: Verify Tests Run the project's full test suite (npm test / cargo test / pytest / go test ./...). If tests fail, report the failures and stop — the menu comes after a green suite: If tests pass: continue to Step 2. Step 2: Detect Environment This determines which menu to show and how cleanup works: State Menu Cleanup ---------------------- GITDIR ==…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Categories
Related skills
- brainstorming
obra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
- systematic-debugging
obra/superpowers
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- writing-plans
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
- using-superpowers
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
265K installs 301K - requesting-code-review
obra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- verification-before-completion
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always