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
Install with Tessl CLI
npx tessl i github:obra/superpowers --skill finishing-a-development-branchOverall
score
91%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description effectively communicates when to use the skill with clear trigger conditions (implementation complete, tests pass) and explains its purpose (guiding integration decisions). However, it could be more specific about the concrete actions it performs and include more natural trigger terms users might actually say when they need this guidance.
Suggestions
Add more natural trigger terms users would say, such as 'pull request', 'ready to merge', 'finished coding', 'done with feature', 'ready for review'
Be more specific about what 'structured options' means - list the actual choices or guidance provided (e.g., 'helps choose between direct merge, creating PR with description, or branch cleanup')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (development work completion) and some actions (merge, PR, cleanup), but lacks comprehensive detail about what specific actions the skill performs beyond 'presenting structured options'. | 2 / 3 |
Completeness | Clearly answers both what ('guides completion of development work by presenting structured options for merge, PR, or cleanup') and when ('when implementation is complete, all tests pass, and you need to decide how to integrate the work'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'merge', 'PR', 'tests pass', and 'implementation complete', but misses common variations users might say like 'pull request', 'ready to merge', 'finished coding', or 'done with feature'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused on the specific moment when development is complete and integration decisions need to be made - distinct from general git skills, testing skills, or code review skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates all best practices: it's concise yet complete, provides executable commands for every path, has clear validation checkpoints (especially the test verification gate and discard confirmation), and is well-organized with a helpful quick reference table. The 'Common Mistakes' and 'Red Flags' sections add value by preventing known failure modes without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable bash commands and git operations throughout. Each option has copy-paste ready code blocks with specific commands for each workflow path. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoints (test verification before proceeding, confirmation for destructive actions). Includes feedback loops for test failures and proper error handling paths. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, a quick reference table for scanning, and appropriate cross-references to related skills. Content is appropriately structured without unnecessary nesting or monolithic blocks. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- Reviewed
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.