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.
Installs into .claude/skills of the current project.
Are you the author of Loop Verifier?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/cobusgreyling-loop-verifier-loop-engineering)
---
name: loop-verifier
description: >
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.
user_invocable: true
---
# Loop 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
1. Every item in the draft exists in the scan input (no hallucinations).
2. Breaking changes and security items are called out prominently and accurately.
3. No invented features or incorrect attribution.
4. Tone matches the project (use any "Release voice" guidance provided).
5. Draft is scannable and not overly long.
6. Includes proper links and thanks where appropriate.
## Output
```markdown
## 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".
