update-project-docs

To keep project documentation in sync with code changes, this skill analyzes your repository structure, detects new modules and architecture updates, and automatically refreshes CLAUDE.md, DECISIONS.md, and SESSION.md to reflect the current state.

The best way to update CLAUDE.md when architecture decisions evolve is to run this skill from the repository root, allowing it to detect structural changes and output guidance for updating architecture references and decision records.

To track major structural changes and new modules in your codebase documentation, this skill reads the repository structure, extracts module inventories, and applies targeted updates to your project files to reflect the latest architecture.

You need to update DECISIONS.md and SESSION.md when architectural decisions evolve or new modules appear, ensuring recent rationale and the latest work notes are accurately recorded alongside code evolution.

Yes, you can automatically refresh project docs by running the skill from the repository root, which analyzes the codebase and outputs documentation changes to CLAUDE.md, DECISIONS.md, and SESSION.md, with an option to commit changes.

This tool works by reading your existing repository structure to detect modules and architecture references, making it suitable for any codebase that utilizes CLAUDE.md, DECISIONS.md, and SESSION.md for documentation.