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

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.

The body delivers fully executable, well-sequenced guidance with strong validation for destructive operations. The main weakness is redundancy between the process steps and the Common Mistakes/Red Flags sections, which inflates token cost.

Suggestions

Collapse the "Red Flags" / "Always-Never" section into the process steps or remove the duplicated "Always:" lines that restate Steps 1, 3, 4, and 5 to recover tokens.

Trim the "Common Mistakes" section to only the mistakes not already implied by the process (e.g. keep force-push caution, drop test-verification which Step 1 already enforces).

Consider moving the Quick Reference table and Common Mistakes into a reference file if the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The core process is lean code, but the "Common Mistakes" and "Red Flags" sections largely restate the process (e.g. "Always: Verify tests before offering options" duplicates Step 1), so it could be tightened.

3 / 5

Actionability

Copy-paste ready commands throughout (git checkout, git merge, git push, and a full gh pr create heredoc) cover the common cases with appropriate placeholders.

5 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation checkpoints: a test gate that says "Stop. Don't proceed to Step 2," typed "discard" confirmation for the destructive option, and a Quick Reference checklist.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and no bundle files, but at ~200 lines inline it is slightly long for an ideal self-contained overview.

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.

The description clearly states both what the skill does and when to use it, with concrete actions and natural trigger phrases. Its main weakness is mild overlap risk with related git skills and slightly terse action coverage.

DimensionReasoningScore

Specificity

"presenting structured options for merge, PR, or cleanup" lists several concrete actions; not a 5 because the sub-actions are terse rather than comprehensive.

4 / 5

Completeness

Explicitly answers both: "Use when implementation is complete, all tests pass..." (when) and "guides completion of development work by presenting structured options for merge, PR, or cleanup" (what).

5 / 5

Trigger Term Quality

Natural phrases like "implementation is complete", "all tests pass", "merge, PR", and "integrate the work" give good coverage, but a few common synonyms (e.g. "wrap up", "finish branch") are missing.

4 / 5

Distinctiveness Conflict Risk

The post-implementation, tests-passing trigger carves a clear niche, but there is minor overlap risk with generic git-merge and worktree-management 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
lucianghinda/superpowers-ruby
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.