finishing-a-development-branch

当实现完成、所有测试通过、需要决定如何集成这份工作时使用

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

88%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 is a well-sequenced, executable workflow with strong validation checkpoints and explicit handling of destructive operations, organized into clear sections with a quick-reference summary. It is lean and action-oriented, with only minor room for tighter prose and no need for external reference files.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude knows git; it does not over-explain concepts, with only minor phrasing that could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready shell commands for each option (env detection, merge, push, worktree removal) covering the common cases including detached HEAD.	5 / 5
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints (test before menu, test on merge result), error-recovery guidance, and a checklist-style quick reference; destructive discard requires exact confirmation.	5 / 5
Progressive Disclosure	Well-organized sections with a quick-reference table and clear single-level structure, but all content is inline with no external references, which is appropriate here yet not fully exemplifying one-level-deep referencing.	4 / 5
	Total	18 / 20 Passed

Description

70%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 is concise and clearly states both the what (deciding how to integrate completed work) and the when (implementation done, tests green), in appropriate third person. It is somewhat thin on enumerating concrete integration options and lacks a fully explicit trigger phrase.

Suggestions

Add an explicit "Use when..." trigger clause enumerating natural phrases a user might say, e.g. "Use when implementation is complete, tests pass, and the user needs to merge, push a PR, or keep the branch."

Name the concrete integration options (local merge, push and open a PR, keep the branch) in the description so the what is comprehensive rather than a single abstract action.

Dimension	Reasoning	Score
Specificity	The description names the domain (finishing a development branch) and the concrete decision-making action, but the only named action is "decide how to integrate," with no enumeration of the integration options.	3 / 5
Completeness	It states what the skill does (decide how to integrate work) and when to use it (implementation complete, tests passing), with the when reasonably explicit but not a standalone explicit trigger clause.	4 / 5
Trigger Term Quality	Natural trigger phrasing like "implementation done, all tests passing, need to decide how to integrate" would plausibly match what a user says, though a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The scenario is fairly niche (post-implementation integration decision) and unlikely to fire for unrelated skills, with only minor overlap risk with general git-workflow skills.	4 / 5
	Total	15 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: jnMetaCode/superpowers-zh
Path: skills/finishing-a-development-branch/SKILL.md
Commit: c68725b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.