CD commit-with-reflection
Git提交与调试反思报告生成技能。用于分析开发过程中的错误、调试步骤和解决方案,生成结构化的中文反思报告,并创建包含报告引用的Git提交。显式请求词:反思提交、智能提交、生成调试报告、commit with reflection。
Git提交与调试反思报告生成技能。用于分析开发过程中的错误、调试步骤和解决方案,生成结构化的中文反思报告,并创建包含报告引用的Git提交。显式请求词:反思提交、智能提交、生成调试报告、commit with reflection。
As a process D 38/100 · Unfinished process — References files that are not bundled: references/report-schema.md, assets/template-feature.md, assets/template-bugfix.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/report-schema.md - warning
missing-refreference to a missing file: assets/template-feature.md - warning
missing-refreference to a missing file: assets/template-bugfix.md - warning
missing-refreference to a missing file: assets/template-refactor.md - warning
missing-refreference to a missing file: scripts/validate-report.js - warning
missing-refreference to a missing file: scripts/extract-errors.js - warning
missing-refreference to a missing file: examples/bugfix-example.md - warning
missing-refreference to a missing file: examples/refactor-example.md - warning
missing-refreference to a missing file: assets/template-custom.md
Process rating: all ten parameters 38/100
- 0Tools and files. 9 referenced file(s) missing: references/report-schema.md, assets/template-feature.md, assets/template-bugfix.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 7 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Steps. 126 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3338 tokens
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 115: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 54 headings
- +3Step-by-step instructions: 126 items
- +4Has examples (23 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.