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

68

Quality

82%

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

The canonical home for this skill is finishing-a-development-branch in obra/superpowers

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured, actionable workflow with strong validation and clear sequencing appropriate to its destructive nature. The main improvement opportunity is tightening redundancy between the process steps and the Common Mistakes/Red Flags sections.

Suggestions

Consolidate 'Common Mistakes' and 'Red Flags' into a single concise checklist, or fold each rule into its relevant step, to reduce redundancy with the process body.

Replace the generic '<test command>' placeholder and the 'npm test / cargo test / pytest / go test' list with a single instruction to run the project's configured test command, keeping examples in a comment.

Tighten the Overview/Core principle lines so they do not restate what the Quick Reference table already conveys.

DimensionReasoningScore

Conciseness

Mostly lean with tables and tight code blocks, but the 'Common Mistakes' and 'Red Flags' sections partly restate guidance already embedded in the process steps, adding some redundancy.

4 / 5

Actionability

Concrete, executable bash commands throughout (git checkout, merge, push, worktree remove, prune) with clear placeholders; minor gaps like the generic '<test command>' and the 'npm test / cargo test / ...' list keep it just short of fully copy-paste ready.

4 / 5

Workflow Clarity

A clearly sequenced 6-step process with explicit validation checkpoints ('Stop. Don't proceed to Step 2', 'Verify tests on merged result', 'Only after merge succeeds'), typed discard confirmation, provenance checks, and Always/Never checklists for this destructive workflow.

5 / 5

Progressive Disclosure

Self-contained SKILL.md with well-organized sections (Overview, Steps 1–6, Quick Reference, Common Mistakes, Red Flags) and a summary table; no bundle files exist, and the inline reference-like material (Common Mistakes/Red Flags) introduces minor organization gaps rather than true multi-file structure.

4 / 5

Total

17

/

20

Passed

Description

83%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.

A strong, third-person description that clearly states both capability and trigger conditions with concrete actions. Minor gains possible from richer trigger synonyms and sharper distinction from generic git skills.

DimensionReasoningScore

Specificity

Names the domain (finishing a dev branch) and several concrete actions — 'presenting structured options for merge, PR, or cleanup' — but stops short of comprehensive coverage of each option's mechanics.

4 / 5

Completeness

Explicitly answers both 'what' (guides completion by presenting structured options for merge/PR/cleanup) and 'when' (Use when implementation is complete, all tests pass, and you need to decide how to integrate the work) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a developer would say ('implementation is complete', 'all tests pass', 'merge', 'PR', 'cleanup'), with good coverage though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The completion-decision niche is fairly distinct, but 'merge/PR/cleanup' language has minor overlap risk with general git or PR-creation skills.

4 / 5

Total

17

/

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
rpamis/comet
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.