What is release-docs?

A release documentation synchroniser that checks which source files changed and updates only the related documentation. It can also prepare a dry-run preview.

It is for syncing documentation with a Git release range, such as the changes between two version tags.

It avoids manually reviewing every document after a release and reduces unrelated documentation changes.

release-docs — Skill for Claude Code by greglas75/zuvo

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/greglas75/zuvo

agentmods

npx agentmods add skills/greglas75/zuvo/release-docs

Made for: Claude Code.

Or install zuvo, the plugin that ships this one along with the rest of its 57 skills, 48 agents, 5 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/greglas75/zuvo/release-docs/github.svg)](https://agentmods.dev/skills/greglas75/zuvo/release-docs)

Your own site

<a href="https://agentmods.dev/skills/greglas75/zuvo/release-docs"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/release-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/greglas75/zuvo/release-docs"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/release-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,570 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Rogue Agent · line 144
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.02570
Opus 5.5	$0.00018	$0.01028
Sonnet 5.5	$0.00009	$0.00514
Haiku 4.5	$0.00004	$0.00257

Measured 1mo ago against content hash cb65d8e94394, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/release-docs/SKILL.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

zuvo:release-docs

Sync documentation with a release. Only updates docs whose source files actually changed.

Mandatory File Loading

Read these files before proceeding:

CORE FILES LOADED:
  1. ../../shared/includes/env-compat.md    — READ
  2. ../../shared/includes/run-logger.md    — READ
  3. ../../shared/includes/retrospective.md    — READ

Argument Parsing

Input	Effect
(no flags)	Auto-detect range from `memory/last-ship.json` or git tags
`<range>`	Explicit git range (e.g., `v1.1.0..v1.2.0`)
`--dry-run`	Show proposed changes without writing

Dispatch follows ../../shared/includes/execution-policy.md through env-compat. Reuse existing authorization within that policy; session restrictions take precedence. Run each required gate and report its actual independence or an unmet requirement.

Phase 0: Determine Range and Suffix

If an explicit <range> argument was provided: use it. Skip remaining steps in this phase.
Else if memory/last-ship.json exists: read the range field (SHA-based, e.g., "abc1234..def5678") and use it directly for git diff. Also read previousTag and newTag for display in the output block. If the artifact uses a legacy version-based range (e.g., "v1.1.0..v1.2.0"), fall back to it but log: "Warning: legacy version-based range — consider re-running zuvo:ship for SHA-based artifact."
Else: derive from git tags.
- Run git describe --tags --abbrev=0 to get the latest tag.
- Run git describe --tags --abbrev=0 <latest-tag>^ to get the previous tag.
- Construct range as <previous-tag>..<latest-tag>.
If no range can be derived after the above steps:
- Interactive environments: ask the user to provide a range explicitly.
- Non-interactive environments (Codex App, Cursor): print [AUTO-DECISION]: no range derivable. Skipping documentation sync. and exit with PASS verdict.
Compute RANGE_SUFFIX for use in evidence and output paths:
- If previousTag and newTag are available: RANGE_SUFFIX = "<previousTag>_<newTag>" (e.g., v1.1.0_v1.2.0)
- Else if range contains tags: extract them (e.g., v1.1.0..v1.2.0 → v1.1.0_v1.2.0)
- Else: use short SHAs from the range (e.g., abc1234_def5678)

Read the full file on GitHub · 201 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · -2 lines cb65d8e94394
1mo ago First seen · 203 lines · 44 tokens per session scan A f9d8146becb4

Subscribe to this mod's changes

release-docs is a skill published in the GitHub repository greglas75/zuvo (8 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,570 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude Code Code review Git and workflow Releases Writing and docs ai-coding claude-code-plugin code-quality codex release

changelog

Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.

reidemeister94/development-skills · 26 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

release-docs