CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/finishing-a-development-branch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable skill with excellent workflow clarity and explicit validation checkpoints throughout. The multi-step process is well-sequenced with clear conditional branching for different environments. The main weakness is some redundancy between the Common Mistakes and Red Flags sections, and the document could be slightly more concise by consolidating repeated guidance about worktree cleanup.

Suggestions

Consolidate the 'Common Mistakes' and 'Red Flags' sections into a single section to eliminate redundancy (e.g., worktree cleanup warnings, test verification reminders appear in both).

DimensionReasoningScore

Conciseness

The skill is mostly efficient and avoids explaining basic git concepts, but the 'Common Mistakes' and 'Red Flags' sections have significant overlap (e.g., worktree cleanup warnings appear in both), and some content in Step 5/6 is repeated. The quick reference table is a nice touch but the overall document could be tightened by ~20%.

2 / 3

Actionability

Provides fully executable bash commands throughout, specific git commands for each option, exact menu text to present, and concrete conditional logic for environment detection. The PR creation command with gh CLI and template body is copy-paste ready.

3 / 3

Workflow Clarity

Excellent multi-step workflow with clear sequencing (verify tests → detect environment → determine base → present options → execute → cleanup). Includes explicit validation checkpoints (test verification before proceeding, test verification after merge, typed confirmation for discard), feedback loops (stop if tests fail), and clear ordering constraints (merge before worktree removal, cd before git worktree remove).

3 / 3

Progressive Disclosure

The content is well-structured with clear headers and a quick reference table, but it's a fairly long monolithic document (~180 lines of content) with no references to external files. The Common Mistakes and Red Flags sections could potentially be split out, though for a standalone skill without bundle files this is acceptable.

2 / 3

Total

10

/

12

Passed

Description

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 effectively communicates when to use the skill with a clear 'Use when...' clause tied to a specific development workflow moment. Its main weakness is moderate vagueness in what the skill actually does - 'presenting structured options' is abstract. The trigger terms cover the core scenario but miss common user phrasings like 'pull request' or 'ready to merge'.

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 such as 'pull request', 'push changes', 'ready to merge', 'done with feature', 'submit for review'

DimensionReasoningScore

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 phrases. However, it misses common variations like 'pull request', 'push changes', 'submit code', 'done coding', 'finish feature', or 'ready to merge'.

2 / 3

Distinctiveness Conflict Risk

This has a clear niche - it's specifically for the post-implementation decision point about how to integrate completed work. The trigger conditions (implementation complete + tests pass + integration decision needed) are quite distinct and unlikely to conflict with general coding, testing, or git skills.

3 / 3

Total

10

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
obra/superpowers
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.