document-release

Compare project documentation with the latest codebase and update files after release.

3|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/mostafasudo/warpy --skill document-release-mostafasudo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-release
Source: https://github.com/mostafasudo/warpy/tree/main/.codex/skills/gstack/document-release
Command: npx skills add https://github.com/mostafasudo/warpy --skill document-release-mostafasudo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Edit, Grep, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating documentation after a software release, ensuring that all project documentation is synchronized with the latest shipped code.

Core Features & Use Cases

  • Documentation Synchronization: Automatically updates README, Architecture, Contributing, and Claude.md files to match the latest shipped code.
  • Change Logging: Generates a polished CHANGELOG with updates on what has changed since the last release.
  • Proactive Updates: Suggests updates proactively after a merge or code shipment.
  • Use Case: After merging a feature branch, this Skill can be used to ensure that all documentation is up-to-date with the new code changes.

Quick Start

Run the document-release skill to update the project documentation after a code shipment.

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 software release?

Automate documentation updates by comparing project files against the latest codebase to synchronize README, Architecture, and Contributing files. The process applies to post-ship software development workflows where maintaining accurate documentation is critical.

What is the best way to synchronize project documentation with the latest shipped code?

Synchronize project documentation by running an automated comparison between the documentation files and the current codebase. This generates a polished CHANGELOG and updates Claude.md files to reflect the new code changes after a merge.

How does automated code synchronization for documentation work after merging a feature branch?

Automated code synchronization works by scanning the codebase using Bash, Grep, and Glob to identify changes after a merge. It then applies updates to README and Architecture files to ensure all project documentation matches the latest shipped code.

Do I need Bash and Grep to update documentation after a code shipment?

Yes, you need Bash, Grep, and Glob tools to scan and compare the latest codebase. The automated documentation update process also requires Read, Write, and Edit tools to apply the necessary changes to project files.

Can I generate a CHANGELOG automatically after a post-ship code merge?

Yes, you can generate a polished CHANGELOG automatically after a code merge. The process logs updates on what has changed since the last release and proactively suggests documentation updates to match the new code.

When should I use automated documentation synchronization in a software development workflow?

Use automated documentation synchronization after merging a feature branch or shipping a code release. It is designed for post-ship workflows where maintaining up-to-date README, Architecture, and Contributing files is critical.