Doc-Code Sync Check
fancyboi999/open-tag
Reconciles documentation with code at the end of a change or as a periodic audit, following a repo rule that code changes and doc changes land in one commit.
Acts as an independent checker for drafted release notes, comparing them with the scan data and returning an APPROVE, REVISE or ESCALATE_HUMAN verdict with evidence.
Install Changelog Draft Verifier
$ npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cobusgreyling/loop-engineering loop-verifier --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/starters/changelog-drafter/.grok/skills/loop-verifier .claude/skills/loop-verifier && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "loop-verifier" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier into .claude/skills/loop-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-verifier", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifierType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cobusgreyling/loop-engineering loop-verifier --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/starters/changelog-drafter/.grok/skills/loop-verifier .agents/skills/loop-verifier && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "loop-verifier" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier into .agents/skills/loop-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-verifier", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cobusgreyling/loop-engineering loop-verifier --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/starters/changelog-drafter/.grok/skills/loop-verifier .cursor/skills/loop-verifier && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "loop-verifier" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier into .cursor/skills/loop-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-verifier", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cobusgreyling/loop-engineering.git --path starters/changelog-drafter/.grok/skills/loop-verifier--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cobusgreyling/loop-engineering loop-verifier --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/starters/changelog-drafter/.grok/skills/loop-verifier .gemini/skills/loop-verifier && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "loop-verifier" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier into .gemini/skills/loop-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-verifier", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cobusgreyling/loop-engineering loop-verifierInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/starters/changelog-drafter/.grok/skills/loop-verifier .github/skills/loop-verifier && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "loop-verifier" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier into .github/skills/loop-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-verifier", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cobusgreyling/loop-engineering loop-verifier --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/starters/changelog-drafter/.grok/skills/loop-verifier .opencode/skills/loop-verifier && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "loop-verifier" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter/.grok/skills/loop-verifier into .opencode/skills/loop-verifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loop-verifier", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
loop-verifier- GitHub stars
- 11k
- Token cost
- ~319 tokens
- SKILL.md length
- 110 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Acts as an independent checker for drafted release notes, comparing them with the scan data and returning an APPROVE, REVISE or ESCALATE_HUMAN verdict with evidence.
- Works in 6 steps: Every item in the draft exists in the… → Breaking changes and security items are… → No invented features or incorrect… → …
- Checking a drafted changelog against the data it was built from
- SKILL.md covers Inputs, Checklist and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The agent receives the raw structured scan output, the draft from the draft-release-notes step and the target and previous versions. It starts from a stance of rejecting or requesting changes unless the draft clearly meets the bar, then works through a checklist: every item exists in the scan input, breaking and security changes are prominent and accurate, nothing is invented or wrongly attributed, tone matches any project voice guidance, the draft is scannable and not overly long, and links and thanks appear where they fit.
The output is a markdown verdict of APPROVE, REVISE or ESCALATE_HUMAN followed by the evidence behind it. When everything holds up, the agent approves and notes that the draft is ready for a human's final review before publishing. The skill exists so that the step that writes the notes never verifies its own work.
When your agent uses it
- Checking a drafted changelog against the data it was built from
- Making sure breaking and security changes are called out in release notes
- Adding an independent review step after draft-release-notes
- Deciding whether a draft needs revision or human escalation
Example prompts
- “Verify this release notes draft against the scan output, comparing version 2.4.0 with 2.3.0.”
- “Check that every entry in the draft exists in the changelog scan and flag anything invented.”
- “Review the draft for missing breaking-change callouts and give me a verdict.”
- “Run the verifier on the latest draft and tell me whether it can go to human review.”
Requirements
- The scan output and a draft from the draft-release-notes step
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- 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.
What it can do on your machine
Read from SKILL.md and the folder at commit 1f1e8a7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Changelog Draft Verifier loads about 319 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 110 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cobusgreyling/loop-engineering at commit 1f1e8a7, republished under its MIT licence (© cobusgreyling). 110 words, ~319 tokens.
Download SKILL.mdSave it as
.claude/skills/loop-verifier/SKILL.md (or your agent's skills folder).- 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
- 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".
© cobusgreyling, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in starters/changelog-drafter/.grok/skills/loop-verifier of cobusgreyling/loop-engineering.
Open the folder on GitHubat commit 1f1e8a7
Compare with similar skills
Changelog Draft Verifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Changelog Draft Verifier this skillcobusgreyling/loop-engineering | 11k | — | ~319 | Automated safety check: Pass | MIT | |
| Doc-Code Sync Checkfancyboi999/open-tag | 201 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Docs GuardamElnagdy/guard-skills | 1.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| ReleasePrefectHQ/fastmcp | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Octocode Code Researchbgauryy/octocode | 946 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Drawio Azuresparklabx/drawio-ai-kit | 652 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Docs Guard
amElnagdy/guard-skills
Checks generated or edited documentation against the source code, flagging invented symbols, outdated samples and unverifiable claims before publishing.
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
Octocode Code Research
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
Drawio Azure
sparklabx/drawio-ai-kit
A skill your agent uses when the user asks for an Azure architecture diagram — VNet/networking, App Service, AKS, landing zone, multi-region, or any diagram built with Azure service icons.
Bulletproof Workflow
artemiimillier/bulletproof
Applies a 12-stage verified workflow, from research to deploy, to non-trivial coding tasks, scaled to lightweight, standard or full mode by task size.
More from cobusgreyling/loop-engineering
All 21 skills in this repoInstall Loop Engineering
cobusgreyling/loop-engineering
Installs Loop Engineering into a project through the single @cobusgreyling/loop CLI, scaffolding a report-only loop and a readiness score.
Loop Constraints Enforcer
cobusgreyling/loop-engineering
Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.
Release Notes Drafter
cobusgreyling/loop-engineering
Turns a structured list of changes from changelog-scan into a categorized, user-facing release notes draft file, and never publishes anything.
Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
Loop Triage Report
cobusgreyling/loop-engineering
Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.
Loop Token Budget Guard
cobusgreyling/loop-engineering
Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
Related
Categories
Questions about Changelog Draft Verifier
What does Changelog Draft Verifier do?
Acts as an independent checker for drafted release notes, comparing them with the scan data and returning an APPROVE, REVISE or ESCALATE_HUMAN verdict with evidence. The agent receives the raw structured scan output, the draft from the draft-release-notes step and the target and previous versions. It starts from a stance of rejecting or requesting changes unless the draft clearly meets the bar, then works through a checklist: every item exists in the scan input, breaking and security changes are prominent and accurate, nothing is invented or wrongly attributed, tone matches any project voice guidance, the draft is scannable and not overly long, and links and thanks appear where they fit.
When should I use Changelog Draft Verifier?
Changelog Draft Verifier fits situations like: checking a drafted changelog against the data it was built from; making sure breaking and security changes are called out in release notes; adding an independent review step after draft-release-notes; deciding whether a draft needs revision or human escalation.
How do I install Changelog Draft Verifier in Claude Code?
Run `npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a claude-code`. Or copy the skill folder (starters/changelog-drafter/.grok/skills/loop-verifier in cobusgreyling/loop-engineering) into .claude/skills/loop-verifier in your project. Claude Code loads it when a task matches its description.
How do I install Changelog Draft Verifier in Codex?
Run `npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a codex`. Or copy the skill folder (starters/changelog-drafter/.grok/skills/loop-verifier in cobusgreyling/loop-engineering) into .agents/skills/loop-verifier in your project. Codex loads it when a task matches its description.
Can I use Changelog Draft Verifier in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cobusgreyling/loop-engineering --skill loop-verifier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loop-verifier, .gemini/skills/loop-verifier, .github/skills/loop-verifier and .opencode/skills/loop-verifier in your project.
What does Changelog Draft Verifier need to run?
SKILL.md names no scripts, command-line tools or credentials: Changelog Draft Verifier is instructions for the agent only. Our summary lists: The scan output and a draft from the draft-release-notes step.
Does Changelog Draft Verifier access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Changelog Draft Verifier safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Changelog Draft Verifier use?
Changelog Draft Verifier is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Changelog Draft Verifier use?
About 319 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Changelog Draft Verifier?
Skills that share tags, products or a category with Changelog Draft Verifier: Doc-Code Sync Check (fancyboi999/open-tag, 201 stars), Docs Guard (amElnagdy/guard-skills, 1.3k stars), Release (PrefectHQ/fastmcp, 28k stars) and Octocode Code Research (bgauryy/octocode, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changelog Draft Verifier?
cobusgreyling (a GitHub user) maintains it in cobusgreyling/loop-engineering, which has 11,429 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: cobusgreyling/loop-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.