Is the Document Release skill free?

Yes. The skill itself is free from DollarDill/beads-superpowers. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Document Release SkillProof Score?

8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 4/5.

How do I install Document Release?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Document Release with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Document Release

Nine-step post-ship docs audit: catches stale README, CHANGELOG and TODOs

by DollarDill · DollarDill/beads-superpowers

Works with setup

Install — copy the command Download source ↗

Test report

Verdict: Works with setup
Score: 8.8/10
Tested: Aug 5, 2026
Environment: Claude Code 2.x (agent harness)

⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (repo unreachable/deleted). The test below is what we measured on Aug 5, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.

Ran both passes on a real branch that shipped a --json flag and a TEXTKIT_TIMEOUT env var into a repo with deliberately stale docs. The skill's CHANGELOG sell-test rewrote a commit-voice entry that never once mentioned the shipped flag into user-facing 'You can now' lines and stripped an internal bd-0412 tag from reader-facing prose; the unaided pass left that entry untouched and also missed the new source file in the CLAUDE.md project tree. It stops and asks before bumping VERSION, a decision the baseline never surfaced at all. The catch is the Beads integration woven through four of its steps: `bd create` returned 'no beads database found' in a fresh repo, so budget `brew install beads` plus a per-repo `bd init` first. Its diagram rule also means an ASCII architecture diagram naming a renamed class gets flagged, not fixed.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 5/5
Triggers reliably 5/5
Output vs. baseline 8/10
Docs & honesty 4/5

What Document Release does

Audits every .md file in a repo against the diff of a finished feature branch, so README tables, ARCHITECTURE notes, CLAUDE.md, CHANGELOG and TODOS match what actually shipped. Applies factual corrections itself, scores CHANGELOG entries against a what-changed/why-care/how-to-use rubric, and refuses to bump VERSION without asking. Triggers on 'update docs', 'documentation audit', 'sync documentation' or a branch about to be merged or PR'd.

How to install Document Release

Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.

Commands — how to trigger Document Release

/document-release Nine-step post-ship docs audit: catches stale README, CHANGELOG and TODOs

It also activates on plain-language prompts like these:

This branch is done, update the docs before I open the PR
Run a documentation audit against this feature branch
Sync the README and CHANGELOG with what we actually shipped

Frequently asked questions

Is the Document Release skill free?: Yes. The skill itself is free from DollarDill/beads-superpowers. SkillProof publishes the install command and an independent test verdict at no cost.
Does Document Release work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Aug 5, 2026. Verdict: Works with setup. Ran both passes on a real branch that shipped a --json flag and a TEXTKIT_TIMEOUT env var into a repo with deliberately stale docs. The skill's CHANGELOG sell-test rewrote a commit-voice entry that never once mentioned the shipped flag into user-facing 'You can now' lines and stripped an internal bd-0412 tag from reader-facing prose; the unaided pass left that entry untouched and also missed the new source file in the CLAUDE.md project tree. It stops and asks before bumping VERSION, a decision the baseline never surfaced at all. The catch is the Beads integration woven through four of its steps: `bd create` returned 'no beads database found' in a fresh repo, so budget `brew install beads` plus a per-repo `bd init` first. Its diagram rule also means an ASCII architecture diagram naming a renamed class gets flagged, not fixed.
What is the Document Release SkillProof Score?: 8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 4/5.
How do I install Document Release?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Document Release with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.