auto-doc

Synchronize project documentation files with codebase changes.

1|Updated Mar 1, 2026

Search Tags:#automation #developer tools #ci/cd #documentation #maintenance #code sync

Ready to run

npx skills add https://github.com/hjemmesidekongen/ai --skill auto-doc-hjemmesidekongen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-doc
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/kronen/skills/auto-doc
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill auto-doc-hjemmesidekongen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your project's documentation accurately reflects the current state of the codebase, preventing outdated information and saving developers time on manual updates.

Core Features & Use Cases

Automated Documentation Updates: Automatically updates CLAUDE.md, ecosystem.json, MEMORY.md, and roadmap.yml based on code changes.
Staleness Detection & Correction: Complements doc-checkpoint by fixing documentation drift after tasks, component additions/removals, or general code changes.
Use Case: After adding a new skill to your project, auto-doc will automatically update the skill counts in CLAUDE.md, add the new skill to the relevant ecosystem.json, and update the roadmap if the task is marked as complete.

Quick Start

Run the auto-doc skill to synchronize documentation with the latest code changes.

Frequently Asked Questions about auto-doc

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

FAQPage Schema

How do I keep project documentation in sync with code changes automatically?▼

Documentation drift occurs when project docs become outdated after multi-file tasks or component modifications. Detecting staleness requires filesystem scanning and diff generation to validate that CLAUDE.md, ecosystem.json, and roadmap.yml accurately reflect the current codebase.

How do I update CLAUDE.md and ecosystem.json after adding a new component to the codebase?▼

Run a documentation synchronization process that scans the filesystem, generates diffs, and performs validation checks to update CLAUDE.md, ecosystem.json, MEMORY.md, and roadmap.yml after component additions, removals, or code drift.

Does automated documentation sync require any dependencies or external libraries?▼

No dependencies are required. The synchronization process relies on filesystem scanning, diff generation, and validation checks to update documentation files without needing additional libraries or external packages.

What is the best way to fix documentation drift after multi-file codebase tasks?▼

Automated documentation synchronization corrects drift by updating CLAUDE.md, ecosystem.json, MEMORY.md, and roadmap.yml based on detected code changes, ensuring project metadata accurately reflects the current state of the codebase without manual intervention.

When should I avoid automated documentation synchronization for code updates?▼

Avoid automated synchronization when manual documentation review is required or when code changes are incomplete, as the process assumes tasks are finished and will update roadmap.yml and ecosystem.json based on the current filesystem state.