update-project-doc

To update project documentation, run an automation skill that compares files like README.md and CLAUDE.md against the live project state. It detects outdated file trees, counts, and timestamps, then performs a leanness audit to flag overly long sections for targeted edits.

You detect and fix stale README file structures by comparing documentation against the live project state using Glob, Grep, and Bash commands. This identifies outdated file trees, timestamps, and counts, allowing you to perform targeted edits with user confirmation to reflect the current codebase.

Yes, you can audit documentation leanness by checking file sizes and section lengths. The process flags overly long files or sections and suggests extraction to dedicated documentation files, ensuring your project docs remain accurate, lean, and easy to maintain.

Yes, the staleness check works with CLAUDE.md and README.md files. It updates these documentation files to reflect the current project state by detecting and flagging outdated file trees, timestamps, counts, and next steps using Glob, Grep, and Bash commands.

You keep project docs accurate and lean by utilizing an automation process that detects stale file trees and performs a leanness audit on file sizes. It uses Glob, Grep, and Bash commands to identify necessary updates and requires user confirmation for targeted edits.