document-release

Scan git diffs and update markdown documentation for releases.

3|Updated Mar 26, 2026

Search Tags:#automation #git #versioning #documentation #release #sync

Ready to run

npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill document-release-the13thnode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/The13thNode/VibeCorp_PromptCEO/tree/main/skills/public/document-release
Command: npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill document-release-the13thnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often falls out of sync with code changes, leading to stale READMEs, outdated architecture diagrams, and missing changelog entries.

Core Features & Use Cases

Scans git diffs to identify changed components.
Validates and updates key documentation files such as CHANGELOG, README, architecture diagrams, and agent registry.
Bumps the project version according to semver and propagates it across relevant files.
Generates a concise report summarizing updates made during a release.

Quick Start

Run the document-release skill before committing a new release to ensure all documentation is current.

Frequently Asked Questions about document-release

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

FAQPage Schema

How do I automatically sync documentation with git changes for a release?▼

Automatically sync documentation by scanning git diffs to identify changed components, then updating key markdown files like CHANGELOG and README for each release commit.

What is the best way to update a CHANGELOG and README from git history?▼

Updating a CHANGELOG and README from git history is best handled by scanning repository diffs, validating version numbers, and propagating updates across markdown files before committing a new release.

How does semver version bumping work when updating markdown architecture diagrams?▼

Semver version bumping works by validating the current version number against git changes and propagating the incremented semantic version across architecture diagrams, README, and CHANGELOG files.

Do I need permission to edit markdown files in the repository to automate documentation releases?▼

Yes, automating documentation releases requires permission to edit markdown files in the repository, access to git history, and reading the CLAUDE.md status table to validate changes.

Can I generate a release report summarizing markdown updates and version changes?▼

Yes, you can generate a concise release report summarizing markdown updates and version changes made during the synchronization process by running the documentation release automation.

Why does documentation fall out of sync with code changes in a git repository?▼

Documentation falls out of sync with code changes because manual updates to READMEs, architecture diagrams, and changelog entries are frequently missed during the release commit process.