CD review-latest-feedback
Review Slack, GitHub, CI, Sentry, Analytics, diagnostics, linked trackers, and app/template, desktop, and package deploy/release lanes. Answer reporters first; fix verified defects, verify delivery, build upvoted features, and recap. Use for scheduled or manual sweeps.
Review Slack, GitHub, CI, Sentry, Analytics, diagnostics, linked trackers, and app/template, desktop, and package deploy/release lanes.
As a process D 38/100 · Unfinished process — References files that are not bundled: references/ci-red-report.md, ...
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5974 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/ci-red-report.md - warning
missing-refreference to a missing file: ... - note
frontmatter-keyunknown frontmatter key "scope" - note
edit-residuethe text marks something as outdated (lines 92): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 38/100
- 0Tools and files. 2 referenced file(s) missing: references/ci-red-report.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
- 30Running it twice. 24 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 70Execution cost. Instruction body is 5974 tokens
- 85Steps. 15 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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)
- +3Output format is not stated: the model decides each time
- -225 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 269: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.