document-release

Automate post-release documentation synchronization across docs, READMEs, and API references.

Updated Feb 9, 2026

Search Tags:#automation #documentation #release #cross-reference #docs-sync #test-plan

Ready to run

npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill document-release-xza85hrf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/Xza85hrf/claude-code-agent-kit/tree/main/.claude/skills/quality/document-release
Command: npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill document-release-xza85hrf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project documentation aligned with the latest release after shipping, reducing drift and manual overhead.

Core Features & Use Cases

Automates release-context detection and doc conformance checks across docs, READMEs, and references.
Updates or flags stale API/docs references, and consolidates a post-release documentation bundle.
Use Case: After releasing a new version, run this skill to verify README, API docs, and changelogs match the codebase.

Quick Start

Run document-release after a ship completes to sync docs with the latest release.

Frequently Asked Questions about document-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate documentation synchronization after a software release?▼

Automate documentation synchronization by running a post-release process to detect release context, identify stale docs, update API references, generate a test plan, and verify cross-references.

What is post-release documentation drift and how do I fix it?▼

Post-release documentation drift occurs when shipped code changes outpace README and API doc updates. Fix it by detecting stale references and updating docs to match the latest Git tag and codebase.

How do I check for stale API references and broken cross-references in my docs?▼

Check for stale API references by executing a documentation conformance verification step that scans docs and READMEs to flag outdated references and validate cross-references against the release.

When should I run a docs sync to align READMEs and contribution guides with a new version?▼

Run a docs sync immediately after a release cycle completes or a Git tag is created to align READMEs, contribution guides, and API references with the latest software release.

Can I generate a test plan for documentation updates after shipping a release?▼

Yes, generate a test plan for documentation updates as part of the post-release synchronization workflow to verify references and summarize changes for release readiness.

What is the best way to consolidate a post-release documentation bundle?▼

Consolidate a post-release documentation bundle by automating the detection of release context, updating flagged stale docs, and summarizing changes to ensure release readiness across all references.