Finishing Development Branch
Close development branch, merge changes, and clean up workspace.
SKILL.md Definition
Finishing a Development Branch
Overview
Guide completion of development work by presenting clear options and handling chosen workflow.
Core principle: Verify tests → Present options → Execute choice → Clean up.
Announce at start: "I'm using the finishing-a-development-branch skill to complete this work."
The Process
Step 1: Verify Tests
Before presenting options, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing:
[Show failures]
Cannot proceed with merge/PR until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
Step 2: Determine Base Branch
# Try common base branches
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Or ask: "This branch split from main - is that correct?"
Step 3: Present Options
Present exactly these 4 options:
Implementation complete. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work
Which option?
Don't add explanation - keep options concise.
Step 4: Execute Choice
Option 1: Merge Locally
# Switch to base branch
git checkout <base-branch>
# Pull latest
git pull
# Merge feature branch
git merge <feature-branch>
# Verify tests on merged result
<test command>
# If tests pass
git branch -d <feature-branch>
Then: Cleanup worktree (Step 5)
Option 2: Push and Create PR
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets of what changed>
## Test Plan
- [ ] <verification steps>
EOF
)"
Then: Cleanup worktree (Step 5)
Option 3: Keep As-Is
Report: "Keeping branch
Don't cleanup worktree.
Option 4: Discard
Confirm first:
This will permanently delete:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path>
Type 'discard' to confirm.
Wait for exact confirmation.
If confirmed:
git checkout <base-branch>
git branch -D <feature-branch>
Then: Cleanup worktree (Step 5)
Step 5: Cleanup Worktree
For Options 1, 2, 4:
Check if in worktree:
git worktree list | grep $(git branch --show-current)
If yes:
git worktree remove <worktree-path>
For Option 3: Keep worktree.
Quick Reference
| Option | Merge | Push | Keep Worktree | Cleanup Branch |
|---|---|---|---|---|
| 1. Merge locally | ✓ | - | - | ✓ |
| 2. Create PR | - | ✓ | ✓ | - |
| 3. Keep as-is | - | - | ✓ | - |
| 4. Discard | - | - | - | ✓ (force) |
Common Mistakes
Skipping test verification
- Problem: Merge broken code, create failing PR
- Fix: Always verify tests before offering options
Open-ended questions
- Problem: "What should I do next?" → ambiguous
- Fix: Present exactly 4 structured options
Automatic worktree cleanup
- Problem: Remove worktree when might need it (Option 2, 3)
- Fix: Only cleanup for Options 1 and 4
No confirmation for discard
- Problem: Accidentally delete work
- Fix: Require typed "discard" confirmation
Red Flags
Never:
- Proceed with failing tests
- Merge without verifying tests on result
- Delete work without confirmation
- Force-push without explicit request
Always:
- Verify tests before offering options
- Present exactly 4 options
- Get typed confirmation for Option 4
- Clean up worktree for Options 1 & 4 only
Integration
Called by:
- subagent-driven-development (Step 7) - After all tasks complete
- executing-plans (Step 5) - After all batches complete
Pairs with:
- using-git-worktrees - Cleans up worktree created by that skill
About Superpowers
Superpowers is a complete software development workflow for your coding agents, built on top of a set of composable "skills".
Philosophy
- Test-Driven Development - Write tests first, always
- Systematic over ad-hoc - Process over guessing
- Complexity reduction - Simplicity as primary goal
- Evidence over claims - Verify before declaring success
Installation
Note: Installation differs by platform. Claude Code has a built-in plugin system. Codex and OpenCode require manual setup.
Claude Code (via Plugin Marketplace)
In Claude Code, register the marketplace first:
/plugin marketplace add obra/superpowers-marketplace
Then install the plugin from this marketplace:
/plugin install superpowers@superpowers-marketplace
Verify Installation
Check that commands appear:
/help
# Should see:
# /superpowers:brainstorm - Interactive design refinement
# /superpowers:write-plan - Create implementation plan
# /superpowers:execute-plan - Execute plan in batches
Links & Support
- Repository: https://github.com/obra/superpowers
- Issues: https://github.com/obra/superpowers/issues
Featured Skills
"Find the perfect 'agent skills' for your project"
ZINC Database
Curated database of commercial compounds for virtual screening.
Zarr Python
Python implementation of chunked, compressed, N-dimensional arrays for scientific data.
USPTO Database
Access to the United States Patent and Trademark Office database.
UniProt Database
Comprehensive, high-quality, and free resource for protein sequences and functional information.
Powerful Agent Skills
Boost your AI performance with our professional skill collection.
Ready to Use
Copy and paste into any agent system supporting skills.
Modular Design
Mix and match 'code skills' to create complex agent behaviors.
Optimized
Each 'agent skill' is tuned for high performance and accuracy.
Open Source
All 'code skills' are open for contributions and customization.
Cross-Platform
Works with various LLMs and agent frameworks.
Safe & Secure
Vetted skills that follow best practices for AI safety.
How it Works
Get started with agent skills in three simple steps.
Pick a Skill
Find the skill you need from our collection.
Read Docs
Understand how the skill works and its constraints.
Copy & Use
Paste the definition into your agent's config.
Test
Verify the results and refine as needed.
Deploy
Launch your specialized AI agent.
What Developers Say
See why developers worldwide choose Agiskills.
Alex Smith
AI Engineer
"Agiskills has completely changed how I build AI agents."
Maria Garcia
Product Manager
"The PDF Specialist skill solved complex document parsing issues for us."
John Doe
Developer
"Professional and well-documented skills. Highly recommend!"
Sarah Lee
Artist
"The Algorithmic Art skill produces incredibly beautiful code."
Chen Wei
Frontend Specialist
"Themes generated by Theme Factory are pixel-perfect."
Robert T.
CTO
"We now use Agiskills as the standard for our AI team."
FAQ
Everything you need to know about Agiskills.
Yes, all public skills are free to copy and use.