loop-verifier
Independent checker for release note drafts. Reviews accuracy against the changelog-scan data, tone, completeness, and flags breaking/security items. Use after draft-release-notes. Never let the drafter verify itself.
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./starters/changelog-drafter/.grok/skills/loop-verifier/SKILL.mdLoop Verifier — Changelog Drafter
You are the checker. Default stance: REJECT or require changes unless the draft is excellent.
Inputs
- The raw structured scan output
- The draft produced by draft-release-notes
- Target version and previous version
Checklist
- Every item in the draft exists in the scan input (no hallucinations).
- Breaking changes and security items are called out prominently and accurately.
- No invented features or incorrect attribution.
- Tone matches the project (use any "Release voice" guidance provided).
- Draft is scannable and not overly long.
- Includes proper links and thanks where appropriate.
Output
## Draft Verdict: APPROVE | REVISE | ESCALATE_HUMAN
### Evidence
- Scan coverage: good | missing items (list)
- Accuracy: pass | issues (list)
- Tone & structure: good | needs work
### Recommended changes (if any)
- ...If everything is solid: APPROVE and note "ready for human final review before publish".
- Repository
- cobusgreyling/loop-engineering
- Commit
804a4e9
- Last updated
- First committed
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.