CtrlK
BlogDocsLog inGet started
Tessl Logo

finishing-a-development-branch

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

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/finishing-a-development-branch/SKILL.md
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 high-quality, well-structured operational skill with strong workflow clarity, explicit validation/feedback loops, and mostly executable guidance. Its only soft spots are placeholder-laden commands and a verbose rationalizations table.

DimensionReasoningScore

Conciseness

The body is lean and task-oriented with code blocks and tables, assuming Claude's competence; the main over-explanation is the 10-row '常见的合理化借口' coaching table and some warning prose that could be trimmed.

4 / 5

Actionability

It provides concrete, mostly executable bash commands (git checkout/merge/branch/worktree), but relies on placeholders like <base-branch>, <feature-branch>, and <测试命令>, and the PR-creation step is described abstractly ('用代码托管平台的工具').

4 / 5

Workflow Clarity

A clear 6-step sequence with explicit validation checkpoints (test gate, re-test on merge result), feedback loops for error recovery (merge failure → stop, cleanup refusal → 3-option menu), and confirmation checklists (the 'discard' word gate) — exemplary for destructive operations.

5 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear sections (步骤 1–6, 快速参考, 常见的合理化借口); at ~200 lines nothing clearly demands splitting into a reference, though a couple of tables could optionally be externalized.

4 / 5

Total

17

/

20

Passed

Description

62%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 has an explicit, concrete 'Use when' trigger and a clear niche, but it describes the action abstractly and omits the natural vocabulary (merge/PR/branch/finish) users would actually say. It is solid but could be sharper.

Suggestions

Enumerate the concrete integration actions in the description, e.g. 'merge back to base, push and open a PR, or keep the branch' instead of the abstract 'decide how to integrate'.

Add natural trigger terms users say — 'finish a branch', 'merge', 'pull request / PR', 'tests are green, ready to ship' — so the skill surfaces for those phrasings.

Keep the explicit '当…时使用' trigger but tighten the 'what' to one concrete clause (e.g. 'integrates a finished development branch by merging, opening a PR, or keeping it').

DimensionReasoningScore

Specificity

The description names the domain ('集成这份工作') and gives concrete trigger conditions ('实现完成、所有测试通过'), but the actual action ('决定如何集成') is abstract and does not enumerate the concrete options (merge / push+PR / keep) the skill performs.

3 / 5

Completeness

It explicitly answers both 'what' (decide how to integrate the work) and 'when' via an explicit 'Use when'-style clause ('当…时使用') with concrete trigger conditions, but the 'what' is abstract rather than listing the concrete integration choices.

4 / 5

Trigger Term Quality

It includes some natural phrases a user would say ('测试通过', '集成', '实现完成'), but misses common synonyms and terms users actually use for this scenario such as merge, pull request/PR, branch, and finish/done.

3 / 5

Distinctiveness Conflict Risk

The trigger conditions (implementation complete, all tests green, deciding integration) carve a specific niche distinct from generic git skills, with only minor overlap risk against broad PR/commit workflows.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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