CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-change

变更校验关卡。分析代码变更,检测文档同步状态,评估变更影响范围。当用户提到变更检查、文档同步、代码审查、提交前检查、diff分析时使用。在设计级变更、重构完成时自动触发。

Quality

75%

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 ./templates/skills/tools/verify-change/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-organized, checklist-driven content with a clean structure and mostly efficient token use, undermined by one material defect: the bundled analyzer script depends on ../../lib/shared.js, which is absent, so the skill's primary command crashes when run. The workflow also lacks a remediation/re-verification loop after warnings.

Suggestions

Fix the broken dependency: scripts/change_analyzer.js requires ../../lib/shared.js which is not in the bundle — vendor the shared helpers into the script (or ship lib/shared.js inside the skill) so "node scripts/change_analyzer.js" actually executes.

Add an explicit feedback loop to the 校验流程: when the analyzer reports ⚠️ (e.g., DESIGN.md not updated), instruct Claude to remediate and re-run the analyzer to confirm the warning clears before concluding 可提交.

Provide a fallback for when the script fails or the environment lacks Node/git (e.g., manual `git diff --stat` checks), so the verification workflow does not dead-end at step 1.

DimensionReasoningScore

Conciseness

The body is dense and instruction-shaped — tables ("代码变更 > 50 行但 DESIGN.md 未更新"), checklists, commands, and templates with almost no concept explanation. The main trimmable fluff is the aphoristic 核心原则 block ("无理由的变更是隐患,无记录的变更是灾难…"), which is philosophical padding with no instructional value — a minor instance of over-explanation, fitting anchor 4 rather than 3 (the rest is efficient) or 5 (the padding exists).

4 / 5

Actionability

Commands are concrete and flags verified ("node scripts/change_analyzer.js --mode staged / -v / --json" all match the script's parser), and thresholds/checklists are specific — but the headline command fails at runtime: change_analyzer.js requires '../../lib/shared.js', which is not in the bundle, so "node scripts/change_analyzer.js" crashes with 'Cannot find module'. The core automated guidance is therefore not executable as shipped, matching anchor 3 (concrete but incomplete, key details missing) rather than 4 (minor gaps).

3 / 5

Workflow Clarity

The 校验流程 lists a clear 5-step sequence and the 前置/后置检查 checklists act as checkpoints, but there is no feedback loop — nothing says what to do when the analyzer emits a ⚠️ warning (update docs, then re-run to confirm it clears) or when the script itself fails — and the verification step depends on the broken script. Anchor 3 (sequence present, validation gaps / remediation implicit) fits better than 4, which would require most checkpoints to be functional and complete.

3 / 5

Progressive Disclosure

The analysis logic is properly externalized into a real bundle file referenced by exact path ("node scripts/change_analyzer.js", verified to exist with matching modes), and sections are clearly headed and scannable. It is not 5: at ~125 lines, content like the 变更记录格式 and 校验报告格式 templates could live in reference files, and the only bundle reference is embedded in a bash block rather than clearly signaled as a navigable reference. Well above anchor 3 (nothing is buried, structure is good).

4 / 5

Total

14

/

20

Passed

Description

80%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 strong description: concrete three-part capability statement, explicit 'use when' triggers with natural phrasing including a synonym, and auto-trigger conditions. Main weakness is trigger distinctiveness — '代码审查' invites conflicts with general code-review skills — plus a few missing trigger synonyms.

Suggestions

Narrow or qualify the "代码审查" trigger (e.g., "变更/文档同步检查" or "代码变更审查") so it does not collide with dedicated code-review skills.

Add natural variations users might say, such as 重构后检查, 变更记录, and 提交信息检查, to broaden trigger coverage.

Mention the test-coverage check and the 校验报告 output in the capability list for fuller coverage of what the skill actually does.

DimensionReasoningScore

Specificity

"分析代码变更,检测文档同步状态,评估变更影响范围" lists three specific concrete actions (analyze changes, detect doc-sync status, assess impact), matching the 'several specific actions with minor gaps' anchor — gaps being test-coverage detection and report generation, which the body provides but the description omits. Not 5 (not comprehensive) and not 3 (more than 1-2 actions, all concrete).

4 / 5

Completeness

Explicitly answers both: what ("分析代码变更,检测文档同步状态,评估变更影响范围") and when ("当用户提到变更检查、文档同步…时使用" plus auto-trigger conditions "在设计级变更、重构完成时自动触发") with concrete trigger phrases. This directly matches the anchor-5 example pattern of capabilities followed by 'Use when…' triggers.

5 / 5

Trigger Term Quality

"变更检查、文档同步、代码审查、提交前检查、diff分析" gives five natural trigger phrases users would actually say, including the English synonym 'diff分析'. A few natural variations are still missing (e.g., 重构, 变更记录, diff 审查), so it falls just short of the comprehensive-synonyms anchor at 5 but well above 'some relevant keywords' at 3.

4 / 5

Distinctiveness Conflict Risk

The core niche (变更校验/文档同步 gating) is fairly distinct, but the trigger "代码审查" (code review) and "提交前检查" are terms squarely owned by dedicated code-review and commit-message skills, creating real overlap risk. Mostly-distinct-with-minor-overlap (4) would require the triggers to be as narrow as the niche; generic broad triggers keep it at 3.

3 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

fengshao1227/ccg-workflow

Path

templates/skills/tools/verify-change/SKILL.md

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.