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.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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 well-crafted workflow skill with strong actionability and clear sequential steps with proper validation checkpoints. The main weakness is moderate redundancy between the Common Mistakes and Red Flags sections, which repeat similar guidance. Overall it's a solid, practical skill that gives Claude clear instructions for each branch completion scenario.

Suggestions

Consolidate 'Common Mistakes' and 'Red Flags' into a single section to eliminate redundancy — they share overlapping guidance on test verification, discard confirmation, worktree cleanup, and staging restrictions.

DimensionReasoningScore

Conciseness

Generally efficient but has some redundancy — the 'Common Mistakes' and 'Red Flags' sections overlap significantly (e.g., both mention test verification, discard confirmation, worktree cleanup, staging docs/plans). The quick reference table is useful but the repeated warnings could be consolidated.

2 / 3

Actionability

Provides concrete, executable bash commands for each option, specific file paths to exclude (docs/plans/*.md), exact text to present to users, and clear sub-skill invocations (kit:create-pr, kit:worktree-cleanup). The 4 options are copy-paste ready with specific commands for both worktree and regular branch scenarios.

3 / 3

Workflow Clarity

Excellent sequential workflow: verify tests → determine base → present options → execute choice. Each step has clear validation checkpoints (tests must pass before proceeding, confirmation required before discard, test verification after merge). Feedback loops are explicit — if tests fail, stop and fix before continuing.

3 / 3

Progressive Disclosure

The content is well-structured with clear headers and a useful quick reference table, but at ~150 lines it's somewhat long for a single file. The Common Mistakes and Red Flags sections could potentially be separated or consolidated. References to sub-skills (kit:create-pr, kit:worktree-cleanup) are well-signaled but no bundle files exist to support deeper reference.

2 / 3

Total

10

/

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.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms, explicit 'Use when' and 'DO NOT TRIGGER' clauses, and occupies a clearly distinct niche in the development workflow. The inclusion of negative trigger conditions is a particularly strong feature that reduces misfire risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: verifying tests pass, presenting four explicit completion options (merge locally, draft PR, keep as-is, discard). Very clear about what the skill does.

3 / 3

Completeness

Clearly answers both what (finalizes branch by verifying tests and presenting completion options) and when (explicit 'Use when...' clause with multiple triggers), plus includes a 'DO NOT TRIGGER' negative boundary condition.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'finish', 'wrap up', 'ship it', 'done with this branch', plus contextual terms like 'merge', 'PR', 'feature branch', 'ready to ship'.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: branch finalization with specific completion options. The negative trigger condition ('DO NOT TRIGGER when tests are still being written') further reduces conflict risk with implementation or testing skills.

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.

Validation11 / 11 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.