skills.rest
kinetas
kinetasCOMMUNITY
Explore all skills by this author →
GitHub

document-release

Align project documentation with shipped changes using diffs and frontmatter guidance.

Updated Mar 11, 2026
Search Tags:#documentation#readme#diff#update#CLAUDE.md#CHANGELOG#post-ship
One-click install
npx skills add https://github.com/kinetas/ai_coding_web --skill document-release-kinetas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/kinetas/ai_coding_web/tree/main/gstack/document-release
Command: npx skills add https://github.com/kinetas/ai_coding_web --skill document-release-kinetas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-ship documentation drift is real. This Skill reads shipped changes, diffs project docs, and updates key docs to reflect what was released, saving time and preventing inconsistencies.

Core Features & Use Cases

  • Reads project docs and the diff, cross-references what shipped, and updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md to match the shipped state.
  • Polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION.
  • Use after a PR is merged or code is shipped to proactively align documentation.

Quick Start

Run the document-release skill after shipping to refresh docs and align everything with what was released.

Frequently Asked Questions about document-release

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

FAQPage Schema
How do I automate post-ship documentation updates after a release?▼

To automate post-ship documentation updates, run this skill after shipping to read your project diffs and automatically align README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files with the released code state.

What is documentation drift and how do I prevent it?▼

Documentation drift happens when project docs become inconsistent with shipped code changes. This skill prevents drift by cross-referencing shipped diffs against existing docs and applying deterministic updates without manual intervention.

How do I keep my CHANGELOG and TODOS aligned with merged PRs?▼

You can keep your CHANGELOG and TODOS aligned by running this skill after a PR merge. It polishes the CHANGELOG voice, cleans up TODOS, and optionally bumps the VERSION file based on shipped changes.

Can I update CLAUDE.md and ARCHITECTURE docs automatically from a diff?▼

Yes, you can update CLAUDE.md and ARCHITECTURE docs automatically. The skill reads project diffs and follows frontmatter guidance to update these key documentation files to match exactly what was released.

Does this documentation update tool require manual configuration to run?▼

No manual configuration is required. The skill operates deterministically by reading diffs and following frontmatter guidance already present in your project docs to apply necessary updates automatically.

Related Skills

Explore More Content & Communication Skills→
aimasteraccaimasteracc
46

document-release

Update project documentation files from branch diffs after PR merges.

Community
Advanced
howdeployhowdeploy
15

document-release

Synchronize project documentation with released code by reading diffs and updating markdown files.

Community
Advanced
badbsallyybadbsallyy

merge-pr

Merge GitHub pull requests via squash and clean up worktrees.

Community
Advanced
monaccodemonaccode
30

changelog-automation

Generate change logs from Git commit messages in Keep a Changelog format.

Official
Intermediate