auto-doc-updater

Update CHANGELOG.md and BLUEPRINT.md after successful builds.

43|8|Updated May 21, 2026

Search Tags:#versioning #documentation #build #blueprint #release-notes #automatic #change-log

Ready to run

npx skills add https://github.com/roedyrustam/vibes-plug --skill auto-doc-updater

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-doc-updater
Source: https://github.com/roedyrustam/vibes-plug/tree/main/skills/auto-doc-updater
Command: npx skills add https://github.com/roedyrustam/vibes-plug --skill auto-doc-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically documents feature changes or bug fixes into CHANGELOG.md and BLUEPRINT.md, ensuring release notes and architectural briefs stay in sync with the codebase.

Core Features & Use Cases

Automatic synchronization of CHANGELOG.md and BLUEPRINT.md after successful builds.
Creates or updates version blocks in CHANGELOG.md and reflects version in BLUEPRINT.md (Version and Last Updated).
Uses precise file-edit operations to avoid breaking structure (e.g., multi_replace_file_content).

Quick Start

Run the auto-doc-updater after a successful build to automatically synchronize CHANGELOG.md and BLUEPRINT.md with the latest changes.

Frequently Asked Questions about auto-doc-updater

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

FAQPage Schema

How do I automatically update CHANGELOG and BLUEPRINT files after a successful build?▼

Automatically update CHANGELOG and BLUEPRINT files by running auto-doc-updater after a successful build, which parses build results to create version blocks in CHANGELOG.md and reflects version and last updated dates in BLUEPRINT.md.

What is the best way to keep release notes and architectural briefs in sync with codebase changes?▼

Keeping release notes and architectural briefs in sync is achieved by automatically documenting feature changes and bug fixes into CHANGELOG.md and BLUEPRINT.md when code changes are verified and builds succeed.

Can I use automatic change-log updates for both frontend and backend development workflows?▼

Yes, automatic change-log updates apply to ongoing development workflows across both frontend and backend projects, ensuring module-level descriptions are logged after each successful build.

Does automatic documentation update work without breaking existing markdown file structures?▼

Automatic documentation update uses precise file-edit operations like multi_replace_file_content to avoid breaking existing markdown file structures when creating or updating version blocks in CHANGELOG.md and BLUEPRINT.md.

When do I need to run the automatic documentation updater for versioning my project?▼

You need to run the automatic documentation updater after a successful build to synchronize CHANGELOG.md and BLUEPRINT.md with the latest code changes, ensuring version blocks and last updated dates stay current.