CD test-failure-mindset
Use when investigating failing tests or deciding whether to change the test or product. Validate test expectations against authoritative intent, trace product and test boundaries, and require evidence for the correction rather than automatic code fixes or test dismissal.
Validate test expectations against authoritative intent, trace product and test boundaries, and require evidence for the correction rather than automatic code…
As a process D 38/100 · Unfinished process — References files that are not bundled: ../root-cause-tracing-process/SKILL.md, ../comprehensive-test-review/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../root-cause-tracing-process/SKILL.md - warning
missing-refreference to a missing file: ../comprehensive-test-review/SKILL.md
Process rating: all ten parameters 38/100
- 0Tools and files. 2 referenced file(s) missing: ../root-cause-tracing-process/SKILL.md, ../comprehensive-test-review/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1107 tokens
- medium 4 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 271: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 10 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.