skills.rest
mariasebarespersona
mariasebarespersonaCOMMUNITY
Explore all skills by this author →
GitHub

document-release

Audit and update documentation by reading diffs and applying factual changes.

Updated Aug 27, 2026
Search Tags:#automation#documentation#consistency#audit#diff#docs
One-click install
npx skills add https://github.com/mariasebarespersona/Tum-AI --skill document-release-mariasebarespersona
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/mariasebarespersona/Tum-AI/tree/main/.claude/skills/document-release
Command: npx skills add https://github.com/mariasebarespersona/Tum-AI --skill document-release-mariasebarespersona

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and update all project documentation after shipping changes, ensuring references stay current and consistency is maintained across CLAUDE.md, restructure-log, skills-inventory, skill.md, PLAN.md, and related materials.

Core Features & Use Cases

  • Reads diffs and cross-references every doc file to find stale references, missing entries, and contradictions.
  • Automatically applies factual updates to documentation and flags narrative gaps for review.
  • Use cases include post-release doc cleanups after PR merges, feature launches, and major code changes.

Quick Start

Run document-release after shipping features to audit docs and automatically apply updates.

Frequently Asked Questions about document-release

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

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

You can update documentation after a release by running a post-release doc audit that reads repository diffs and applies factual updates to keep references current across all project files.

What is the best way to find stale references in project docs after a PR merge?▼

Finding stale references after a PR merge is done by cross-referencing the repository diff against documentation files to identify missing entries, contradictions, and outdated information.

Does the doc audit require repository diff access to check consistency?▼

Yes, repository diff access is required to perform the documentation consistency check, as the audit reads the diff to cross-reference every doc file and apply version-appropriate updates.

What are the limitations of automating documentation updates after shipping changes?▼

Automated documentation updates apply factual changes directly but flag narrative gaps for human review, meaning contradictions requiring contextual interpretation are not resolved automatically.

When do I need to run a post-release documentation cleanup?▼

You need a post-release documentation cleanup after shipping features, merging PRs, or launching major code changes to ensure cross-references stay accurate and stale references are removed.

Related Skills

Explore More Content & Communication Skills→
forcedotcomforcedotcom
1.0k

verification

Validate code changes with compile, lint, diagnostics, tests, and bundling.

Official
Intermediate
jeffrigbyjeffrigby
7

docs-maintenance

Synchronize project documentation with code changes across CLAUDE.md, README.md, CHANGELOG.md, and /docs.

Community
Basic
onlypfachionlypfachi

document-release

Cross-reference shipped changes and update README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, and CHANGELOG.

Community
Advanced
burgebjburgebj

skill-doc-sync

Synchronize project markdown documentation with git diff code changes.

Community
Advanced