CtrlK
BlogDocsLog inGet started
Tessl Logo

close-github-worktree-done

在用户显式 @ 本 skill 或明确下达「关闭 worktree 并完成需求」类指令时:将指定分支关联的 GitHub Issue 关闭(可选并确认),移除本地 git worktree 目录与本地分支(不删除远程分支)。 必须在 master 分支上执行。用户可指定要关闭的分支名;若未指定,列出所有 worktree 供用户选择。 不得因仅提及 GitHub、issue、worktree、git 等词而自动套用;须以用户主动调用本工作流为准。

69

Quality

84%

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

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 tightly written, executable destructive-workflow skill with strong validation checkpoints and feedback loops throughout Steps 0–5. The main weakness is minor: referenced helper scripts live outside this skill's bundle.

DimensionReasoningScore

Conciseness

Mostly lean, instruction-focused prose with concrete commands and no padding about concepts Claude already knows; the occasional rationale notes (e.g., '顺序说明') are justified for a destructive workflow but could be trimmed slightly.

4 / 5

Actionability

Concrete, mostly executable commands throughout (git branch --show-current, git worktree list, git worktree remove [--force], git branch -d) plus full MCP CallMcpTool argument blocks, but placeholders (<TARGET_ROOT>, <issue号>) and conditional handling ('除非…按提示处理', '必要时加') leave minor gaps versus copy-paste readiness.

4 / 5

Workflow Clarity

Steps 0–5 are clearly sequenced with explicit validation checkpoints for a destructive operation: master-branch guard, TARGET_ROOT != MAIN_ROOT check, dirty-tree consent, fetch/merge then git branch --merged, AskQuestion before deleting unmerged branches, and issue-state check before closing — plus feedback loops for -d refusal and MCP failure.

5 / 5

Progressive Disclosure

Well-organized into clear sections (固定参数, 硬性约束, 工作流, 注意事项) as a focused single-file workflow, but it references external scripts (.cursor/skills/github-worktree/scripts/git-worktree.ps1/.sh) that are not present in the local bundle, a minor navigation/organization gap.

4 / 5

Total

17

/

20

Passed

Description

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

A specific, well-scoped description that clearly states capabilities, trigger conditions, and the master-branch constraint while explicitly guarding against accidental invocation. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists several concrete actions — '将指定分支关联的 GitHub Issue 关闭(可选并确认)', '移除本地 git worktree 目录与本地分支', '必须在 master 分支上执行', branch selection logic — with only minor coverage gaps (e.g., the non-deletion of the remote branch is stated as a constraint rather than a capability).

4 / 5

Completeness

Explicitly answers both what ('关闭 Issue / 移除 worktree 与本地分支') and when ('在用户显式 @ 本 skill 或明确下达「关闭 worktree 并完成需求」类指令时…必须在 master 分支上执行') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrase '关闭 worktree 并完成需求' plus relevant keywords (worktree, 分支, GitHub Issue, master) give good coverage, though a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (closing a worktree + finishing a requirement on master for TencentBlueKing/bk-ci) with an explicit anti-drift clause — '不得因仅提及 GitHub、issue、worktree、git 等词而自动套用' — minimizing conflict risk.

5 / 5

Total

18

/

20

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
TencentBlueKing/bk-ci
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.