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
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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've finished coding.
Suggestions
Add more natural trigger terms users would say, such as 'pull request', 'ready to merge', 'done coding', 'finished the feature', or 'ship it'
Expand the specific actions beyond 'presenting structured options' - describe what guidance or outputs the skill actually provides (e.g., 'generates PR descriptions', 'suggests branch cleanup commands')
| 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 ship', 'done coding', or 'finished feature'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused on the specific moment when development is complete and integration decisions are needed - 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 strong workflow design with clear validation checkpoints, concrete executable commands, and well-structured content. The four-option decision framework is cleanly presented, and the common mistakes/red flags sections add valuable guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only necessary information. It assumes Claude's competence with git commands and doesn't explain basic concepts. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable bash commands throughout, with specific git and gh CLI commands that are copy-paste ready. The PR creation template and test verification commands are concrete and complete. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 1-5), explicit validation checkpoints (test verification before proceeding), and feedback loops (stop if tests fail). The quick reference table provides clear decision matrix. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections: overview, step-by-step process, quick reference table, common mistakes, and red flags. References to related skills (epic-journey-update, using-git-worktrees) are clearly signaled without deep nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- projectbluefin/dakota
- Commit
f062bf8
- 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.