document-release

Analyze git diffs and update stale project documentation after releases.

Updated Apr 20, 2026

Search Tags:#automation #documentation #release #docs #version-control #diff-analysis

Ready to run

npx skills add https://github.com/aspectrr/denchclaw-workspace --skill document-release-aspectrr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/aspectrr/denchclaw-workspace/tree/main/skills/gstack/document-release
Command: npx skills add https://github.com/aspectrr/denchclaw-workspace --skill document-release-aspectrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures project documentation stays in sync with shipped features by auditing diffs and updating stale docs.

Core Features & Use Cases

Inventory and locate documentation files (README.md, ARCHITECTURE.md, CHANGELOG.md, TODOS.md, AGENTS.md, etc.)
Analyze git diffs to identify drift between code and docs
Update affected documentation across core docs and changelogs
Commit changes with a standardized message and provide a summary

Quick Start

Run this skill to scan the repository, identify drifted docs, and update them to match 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 keep project documentation in sync with shipped features after a release?▼

You can automate keeping documentation in sync with shipped features by analyzing git diffs after releases, detecting drift between code and docs, and automatically updating affected files like README.md and CHANGELOG.md.

What is documentation drift and how does diff analysis detect it?▼

Documentation drift occurs when project docs no longer reflect the current codebase. Diff analysis detects this drift by comparing git changes after a release against the existing content in files like ARCHITECTURE.md and TODOS.md to identify outdated information.

Can I automatically update a CHANGELOG.md and README.md based on git commits?▼

Yes, you can automatically update a CHANGELOG.md and README.md based on git commits by running an inventory scan to locate core docs, analyzing the commit diffs, and applying automated updates to reflect the latest shipped features.

Does this automated documentation update approach work without external dependencies?▼

Yes, this automated documentation update approach works without external dependencies, as it independently inventories core docs, performs diff analysis, generates updates, and commits changes with a standardized message directly within your repository.

What is the best way to automate version control for project documentation?▼

The best way to automate version control for project documentation is to use a tool that inventories your docs, analyzes code diffs, applies updates to stale files, and automatically commits the changes with a standardized message after every release.

When should I not use automated diff analysis for documentation updates?▼

You should avoid using automated diff analysis for documentation updates when a repository lacks core docs like README.md or ARCHITECTURE.md, as the process specifically relies on inventorying and updating these established files to ensure docs reflect current code.