CtrlK
BlogDocsLog inGet started
Tessl Logo

finish-branch

Finalizes a development branch by verifying tests pass, then presenting four completion options (merge locally, draft PR, keep as-is, or discard). Use when implementation is done, a feature branch is ready to ship, work needs to be merged or a PR created, or the user says "finish", "wrap up", "ship it", or "done with this branch". DO NOT TRIGGER when tests are still being written or implementation is incomplete.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 skill body with a clear sequenced workflow and explicit validation/confirmation checkpoints. Its main weakness is redundancy: the closing Common Mistakes, Red Flags, and Always sections restate rules already embedded in the process steps.

Suggestions

Consolidate the repeated rules — "Do NOT stage docs/plans/*.md", "verify tests before options", and "no automatic worktree cleanup" each appear 3–4 times across the process, Common Mistakes, and Red Flags; state each once in the process and drop the duplications.

Trim the Common Mistakes, Red Flags, and Always sections to only net-new caveats not already covered in Step 1–4, cutting the body's token cost without losing guidance.

Replace the bare "<test command>" placeholder with a note to reuse the project's detected runner (already named at Step 1: npm test / cargo test / pytest / go test) so the re-verify step is copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient imperative guidance, but several rules are restated 3–4 times — "Do NOT stage docs/plans/*.md" appears in Option 1, Option 2, Common Mistakes, and Red Flags, and "verify tests"/"no auto worktree cleanup" recur similarly. It is not level 3 because the Common Mistakes, Red Flags, and Always sections substantially duplicate the process steps rather than earning every token.

2 / 3

Actionability

Provides real executable bash (git pull --autostash, git merge, git push -u origin, the worktree path extraction one-liner) plus exact menu and confirmation text. Placeholders like <feature-branch> denote genuinely variable values, so this is concrete and actionable rather than pseudocode — not level 2.

3 / 3

Workflow Clarity

Clear Step 1–4 sequence with explicit validation checkpoints ("Stop. Don't proceed to Step 2" on failure, re-verify tests after merge) and a typed-confirmation feedback loop for the destructive discard. Not level 2 because checkpoints and error-recovery paths are explicit.

3 / 3

Progressive Disclosure

No bundle files exist and the skill needs none; the body is self-contained with well-organized sections (Overview, Process, Quick Reference, Common Mistakes, Red Flags, Integration). Per the simple-skill note, well-organized sections without external references score 3. Not level 2 because structure and navigation are clear.

3 / 3

Total

11

/

12

Passed

Description

100%

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 states concrete actions, gives explicit use-when triggers with natural phrasing, and adds a negative trigger guard. It covers what, when, and how to distinguish it from sibling skills.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions: "verifying tests pass, then presenting four completion options (merge locally, draft PR, keep as-is, or discard)". It is not level 2 because it enumerates several specific actions rather than naming only a domain and a few.

3 / 3

Completeness

Explicitly answers both what ("Finalizes a development branch by verifying tests pass, then presenting four completion options") and when ("Use when implementation is done..." plus "DO NOT TRIGGER when tests are still being written"). Both halves are explicit, satisfying the level-3 anchor.

3 / 3

Trigger Term Quality

Includes natural phrases users actually say — "finish", "wrap up", "ship it", "done with this branch" — plus situational triggers like "feature branch is ready to ship". Good coverage of common variations, so not level 2.

3 / 3

Distinctiveness Conflict Risk

A clear niche (finishing a branch) with distinct triggers unlikely to fire for unrelated skills; the "DO NOT TRIGGER" guard further reduces misfires. Not level 2 because the triggers are specific and bounded.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shousper/claude-kit
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.