finishing-a-development-branch
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
88
83%
Does it follow best practices?
Impact
98%
1.92xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
85%Feature Branch Completion Automation
Workflow options and safety gates
Tests before options
0%
100%
Exactly 4 options
0%
100%
Options without explanation
0%
100%
Discard shows deletion preview
33%
100%
Discard requires 'discard' keyword
0%
100%
Worktree kept for PR option
100%
100%
Worktree kept for keep-as-is option
0%
100%
Worktree removed after merge
0%
100%
Worktree removed after discard
0%
100%
95%
35%Standardized PR Submission Script
PR creation format and push safety
Push with -u flag
100%
100%
Uses gh pr create
100%
100%
PR body has Summary section
100%
100%
Summary uses bullet points
0%
66%
PR body has Test Plan section
0%
100%
Test Plan uses checkboxes
33%
100%
No force push
100%
100%
100%
20%Local Feature Branch Integration
Local merge with test re-verification
Checkout base branch first
100%
100%
Pull latest before merge
100%
100%
Merges feature branch in
100%
100%
Re-runs tests after merge
100%
100%
Deletes branch with -d flag
100%
100%
Cleans up worktree
0%
100%
- Repository
- obra/superpowers
- Commit
b7a8f76
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.