---
name: Loop Verifier
slug: loop-verifier-2
category: Quality
description: Loop Verifier reviews release note drafts against the changelog scan data to flag hallucinations, missing breaking or security items, and tone problems. Use it after draft-release-notes to independently check accuracy before human review.
github: "https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier"
language: JavaScript
stars: 10380
forks: 1410
install: "npx degit https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier ~/.claude/skills/loop-verifier"
installs_to: ~/.claude/skills/loop-verifier
source_path: starters/changelog-drafter/.grok/skills/loop-verifier/SKILL.md
collection_size: 23
category_size: 1354
collection_url: "https://dirskills.com/collections/cobusgreyling/loop-engineering"
added: 2026-08-15T06:50:31.919Z
last_synced: 2026-08-15T06:50:31.919Z
canonical_url: "https://dirskills.com/skills/loop-verifier-2"
---

# Loop Verifier

Loop Verifier reviews release note drafts against the changelog scan data to flag hallucinations, missing breaking or security items, and tone problems. Use it after draft-release-notes to independently check accuracy before human review.

**Install:**

```bash
npx degit https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier ~/.claude/skills/loop-verifier
```

## README

# 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".