CtrlK
BlogDocsLog inGet started
Tessl Logo

finishing-a-development-branch

当实现完成、所有测试通过、需要决定如何集成工作时使用——通过提供合并、PR 或清理等结构化选项来引导开发工作的收尾

71

Quality

88%

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

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally actionable and concise with a well-sequenced, validated workflow backed by red-lines and common-mistake sections — strong on execution. Its only gap is that all content lives inline in one file with no bundle references, leaving progressive disclosure flat.

Suggestions

Consider extracting the '常见错误' and '红线' checklists into a reference file (e.g. CHECKLISTS.md) and pointing to it one level deep, which would raise progressive_disclosure without losing the lean overview.

No change needed to conciseness, actionability, or workflow_clarity — these are already at the top anchor.

DimensionReasoningScore

Conciseness

Lean and efficient: assumes git/worktree competence, uses tight bash blocks and tables, and avoids explaining what a branch, worktree, or PR is — every section earns its place.

3 / 3

Actionability

Fully executable bash commands throughout (worktree detection, merge, push, gh pr create, cleanup), with exact confirmation prompts and concrete menu text to display verbatim — copy-paste ready.

3 / 3

Workflow Clarity

A clear 6-step sequence with explicit validation checkpoints (test-before-options, verify-after-merge) and feedback loops (test fails → stop; discard requires 'discard' confirmation), capped by red-line and common-mistake checklists.

3 / 3

Progressive Disclosure

Well-organized into clear sections but it is a single monolithic SKILL.md with no external reference files; the depth is appropriate yet progressive disclosure is one-level-flat with nothing to split out.

2 / 3

Total

11

/

12

Passed

Description

85%

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 specific and complete, clearly stating both what the skill does and when to use it with concrete integration options. Trigger phrasing is functional but leans on paraphrase rather than the exact phrases users naturally say, leaving minor room for improvement.

Suggestions

Add concrete natural-language trigger phrases users would actually say (e.g. 'merge this branch', 'open a PR', 'clean up the worktree') alongside the '当...时使用' clause to improve trigger_term_quality.

Keep the concise single-sentence form; do not pad it — the current length already earns its tokens.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '提供合并、PR 或清理等结构化选项' and '引导开发工作的收尾' — naming specific integration paths rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ('通过...结构化选项来引导...收尾') and when ('当实现完成、所有测试通过、需要决定如何集成工作时使用'), satisfying the explicit trigger requirement.

3 / 3

Trigger Term Quality

Includes some natural terms a user would say ('实现完成', '测试通过', '集成'), but relies on paraphrase ('当...时使用') rather than the common variations users voice like 'merge this branch', 'open a PR', or 'clean up'.

2 / 3

Distinctiveness Conflict Risk

The narrow 'finishing a development branch' niche with completion+tests-passing triggers is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.