skills.rest
geoffreywoo
geoffreywooCOMMUNITY
Explore all skills by this author →
Website𝕏@geoffreywooGitHub

document-release

Automate post-ship documentation updates from release diffs across project docs.

1|Updated Feb 27, 2026
Search Tags:#changelog#documentation#diff#sync#docs#version-bump#post-ship
One-click install
npx skills add https://github.com/geoffreywoo/clawfable --skill document-release-geoffreywoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/document-release
Command: npx skills add https://github.com/geoffreywoo/clawfable --skill document-release-geoffreywoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates post-ship documentation maintenance to ensure published work aligns across the project docs. It reads the diff from the release, updates README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md to reflect what shipped, polishes CHANGELOG language, tidies TODOS, and can bump the repo VERSION when requested.

Core Features & Use Cases

  • Auto-sync: Post-ship docs stay consistent by applying shipped changes to README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md.
  • CHANGELOG polish: Polishes changelog language without overwriting existing entries.
  • Todos cleanup: Removes obsolete or fulfilled todos and refreshes pending ones.
  • Version bump: Optionally bumps VERSION as part of the release docs workflow.

Quick Start

Run the document-release workflow after shipping code to automatically align docs, polish the changelog, and optionally bump the version.

Frequently Asked Questions about document-release

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

FAQPage Schema
How do I automatically update documentation after a release?▼

Automate post-ship documentation maintenance by reading release diffs to update README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md so published work aligns across project docs.

What is the best way to sync a changelog with shipped code changes?▼

Sync a changelog with shipped code by reading diffs from the release and polishing CHANGELOG language without overwriting existing entries to accurately reflect what shipped.

Can I automatically bump a repo VERSION when syncing docs post-ship?▼

You can bump the repo VERSION as part of the release docs workflow when requested, applying diff-based updates to ensure documentation and versioning stay consistent after shipping.

How does diff-based documentation update work for project files?▼

Diff-based documentation updates work by reading the release diff, applying safe auto-updates to project docs, and prompting for human confirmation when changes require review.

How do I clean up obsolete TODOS after shipping a release?▼

Clean up obsolete TODOS after shipping by automatically removing fulfilled todos and refreshing pending ones to reflect the current project state based on the release diff.

When should I manually review documentation changes during a version bump?▼

You should manually review documentation changes during a version bump when the diff-based update detects changes that require human confirmation, applying auto-updates only when safe.

Related Skills

Explore More Content & Communication Skills→
chriswesttchriswestt

document-release

Update README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md after shipping changes.

Community
Advanced
scanbottscanbott

ship

Automate release workflows by merging branches, running tests, bumping versions, and creating PRs.

Community
Advanced
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
stayconnectquickstayconnectquick

document-release

Update core project docs after shipped code changes.

Community
Intermediate