skills.rest
forbotsake
forbotsakeOFFICIAL
Explore all skills by this author →
GitHub

document-release

Synchronize post-release documentation with code changes after a PR merge.

5|1|Updated Apr 5, 2026
Search Tags:#automation#changelog#documentation#synchronization#claude#release#docs
One-click install
npx skills add https://github.com/forbotsake/forbotsake --skill document-release-forbotsake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/forbotsake/forbotsake/tree/main/.claude/skills/gstack/document-release
Command: npx skills add https://github.com/forbotsake/forbotsake --skill document-release-forbotsake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-ship documentation often drifts after code is shipped. This skill automates the synchronization of shipped changes with project docs, ensuring readers see up-to-date information.

Core Features & Use Cases

  • Reads the project docs and the diff from the latest release to identify what changed.
  • Updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md to reflect shipped changes.
  • Polishes the CHANGELOG voice, cleans up TODOS, and optionally bumps the VERSION when requested.

Quick Start

Run the document-release skill after shipping to sync all docs with the latest code.

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 updates after a release merge?▼

Automate documentation updates after a release by running a skill that reads the latest code diff and synchronizes README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to reflect shipped changes.

What is the best way to keep a project CHANGELOG synchronized with code changes?▼

Keeping a CHANGELOG synchronized involves reading post-merge diffs to identify modifications, then polishing the changelog voice and cleaning up TODOS to ensure the documentation accurately reflects the latest release state.

Can I automatically bump the VERSION in my docs when a release ships?▼

Yes, you can bump the VERSION in your project documentation automatically. When requested after a shipped release, the documentation synchronization process identifies version changes and updates the version file accordingly.

Does the document-release skill work without external dependencies?▼

Yes, the post-ship documentation synchronization requires no external dependencies. It operates autonomously to read project diffs and update internal project docs like README and CONTRIBUTING after a PR merge.

When should I run post-release documentation synchronization?▼

Run documentation synchronization immediately after shipping a release or merging a PR. This ensures your project docs, including ARCHITECTURE and CLAUDE.md, accurately reflect the latest code changes before readers access them.

Why does post-ship documentation drift from the actual codebase?▼

Post-ship documentation drifts because manual updates are often forgotten after code is shipped. Automating the synchronization of diffs with README and CHANGELOG files prevents this documentation staleness.

Related Skills

Explore More Content & Communication Skills→
TioSavichTioSavich

ship

Merge base branch, run tests, bump version, update changelog, commit, push, and create a pull request.

Community
Advanced
QredenceQredence
108

changelog-generator

Convert git commits into customer-facing release notes.

Official
Intermediate
tan-yong-shengtan-yong-sheng
1

gstack-ship

Coordinate merges, tests, version bumps, changelog updates, and PR creation.

Community
Advanced
MFS-codeMFS-code
8

document-release

Audit markdown documentation against code diffs and update release notes.

Community
Advanced