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
91
87%
Does it follow best practices?
Impact
98%
1.92xAverage score across 3 eval scenarios
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.
The description has strong completeness with an explicit 'Use when' clause and clear trigger conditions, and it occupies a distinct niche in the development workflow. However, it could be more specific about what concrete actions the skill performs beyond 'presenting structured options,' and could benefit from additional natural trigger term variations that developers might use.
Suggestions
Add more specific concrete actions the skill performs, e.g., 'Presents structured options for merging branches, creating pull requests, squashing commits, or cleaning up feature branches'
Include additional natural trigger term variations like 'pull request', 'push changes', 'ready to merge', 'submit code', 'done with feature' to improve keyword coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (development workflow completion) and some actions (merge, PR, cleanup), but the actions are presented as options rather than concrete capabilities the skill performs. 'Guides completion of development work by presenting structured options' is somewhat vague about what it actually does. | 2 / 3 |
Completeness | Explicitly 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). The 'Use when...' clause is present and specific. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'merge', 'PR', 'tests pass', 'cleanup', and 'implementation is complete', which are natural developer terms. However, it misses common variations like 'pull request', 'push changes', 'submit code', 'done coding', 'finish task', or 'ready to merge'. | 2 / 3 |
Distinctiveness Conflict Risk | This has a clear niche: post-implementation decision-making about code integration. The specific trigger conditions (implementation complete, tests passing, deciding integration method) make it unlikely to conflict with general coding, testing, or git 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 file that is concise, actionable, and well-structured. It provides clear executable commands for each workflow path, includes explicit validation checkpoints (test verification before and after merge, typed confirmation for destructive operations), and avoids unnecessary explanation. The quick reference table and common mistakes sections add value without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient throughout. It doesn't explain what git is, what merging means, or other concepts Claude already knows. Every section serves a clear purpose, and the quick reference table is a compact summary rather than redundant content. | 3 / 3 |
Actionability | Provides fully executable bash commands for every option, exact text templates for PR bodies and confirmation prompts, and specific decision logic (e.g., 'If tests fail: Stop. Don't proceed to Step 2'). The 4 options are copy-paste ready with concrete commands. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (verify tests → determine base → present options → execute → cleanup) with explicit validation checkpoints: tests must pass before proceeding, tests are re-run after merge, typed confirmation is required before discard. The feedback loop for test failures is explicit, and the Common Mistakes / Red Flags sections reinforce critical guardrails. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (process steps, quick reference table, common mistakes, red flags, integration). For a skill with no bundle files, the structure is appropriate—nothing is monolithic, and the integration section clearly signals relationships to other skills without nested references. | 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
- roman01la/skills-agents
- Commit
45417f2
- 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.