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

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/finishing-a-development-branch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

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

This is a well-engineered destructive-operation skill: lean, fully actionable, with thorough validation checkpoints and feedback loops that protect against data loss. The only marginal gaps are minor conciseness trims and the deliberately forge-agnostic PR step.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explanations of git/worktrees), and gives purposeful code comments; only minor trim opportunities exist such as the 'Announce at start' line and the length of the Common Rationalizations table.

4 / 5

Actionability

Concrete, executable bash is provided throughout (GIT_DIR capture, git push, worktree remove) with clearly templated placeholders; the only soft spot is the forge-agnostic PR-creation step, which is intentionally left flexible rather than copy-paste.

4 / 5

Workflow Clarity

A clearly sequenced six-step workflow is packed with explicit validation checkpoints (stop on red tests, verify merged result, typed 'discard' confirmation, worktree-removal refusal handling) plus a Quick Reference table and Common Rationalizations that function as checklists — satisfying the destructive-skill validation requirement.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is a cohesive self-contained workflow; the single SKILL.md is well-organized with clear Step 1–6 headers plus reference tables, which is appropriate structure for a skill with no need for external references.

5 / 5

Total

18

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 a strong, explicit 'Use when' trigger and a reasonably distinct niche, but it underspecifies the concrete actions the skill performs and uses second-person voice. Stating the actual options (merge, push/PR, keep, discard) and switching to third person would lift it.

Suggestions

Name the concrete actions the skill offers, e.g. 'merge locally, push and open a PR, keep the branch, or discard it' so the 'what' is explicit.

Rewrite in third person to match the rubric's voice expectation, e.g. 'Decides how to integrate completed, green-tested work — merge locally, push and open a PR, keep, or discard.'

Add a couple of trigger synonyms such as 'finishing a branch' or 'wrapping up a feature' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (finished implementation, passing tests, integration) and a decision verb, but does not enumerate the concrete actions the skill performs (merge/push/keep/discard) — those live only in the body. Reduced from 3 to 2 because the description uses second person ('you need to decide how to integrate the work'), which the rubric penalizes by one specificity point.

2 / 5

Completeness

It explicitly provides a 'Use when...' trigger (implementation complete, tests pass, need to decide integration) and an implied 'what' (decide how to integrate the work), but the 'what' is not stated as concrete actions, keeping it just short of a 5.

4 / 5

Trigger Term Quality

Phrases like 'implementation is complete', 'all tests pass', and 'integrate the work' are natural things a user would say when needing this skill, giving good keyword coverage, though a few synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

The completion-plus-green-tests framing carves a fairly distinct end-of-branch integration niche, with only minor overlap risk against generic commit/PR skills.

4 / 5

Total

14

/

20

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.

Validation16 / 16 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.