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:projectbluefin/dakota --skill finishing-a-development-branch92
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 and has a distinct niche in the development workflow. However, it could be more specific about the concrete actions performed and include more natural language variations that users might employ when they've finished coding.
Suggestions
Add more natural trigger term variations like 'pull request', 'done coding', 'ready to commit', 'finished feature', or 'code complete'
Expand specificity by detailing what the structured options include (e.g., 'presents options including direct merge to main, creating a PR with description, branch cleanup, or squashing commits')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (development work completion) and some actions ('presenting structured options for merge, PR, or cleanup'), but lacks comprehensive detail about what specific actions the skill performs beyond presenting 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') with explicit trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'merge', 'PR', 'tests pass', and 'cleanup', but misses common variations users might say like 'pull request', 'done coding', 'ready to commit', 'finished implementation', or 'code review'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused on the specific moment after implementation is complete and tests pass, with distinct triggers around integration decisions. Unlikely to conflict with general coding or testing 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 demonstrates strong workflow design with clear validation checkpoints, executable commands, and well-organized structure. The four-option decision framework is concrete and actionable, with appropriate safeguards (typed confirmation for destructive actions). The Common Mistakes and 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 code blocks are complete and concrete, not pseudocode. | 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-structured with clear sections, a quick reference table for scanning, and appropriate references to related skills (epic-journey-update, using-git-worktrees). Content is appropriately organized without being monolithic. | 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.
- 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.