docs-maintenance

To sync project documentation with the filesystem, run the Python maintenance script to automatically regenerate docs/tree.md, ensuring your documentation accurately mirrors the current repository structure without manual reconciliation.

Documentation drift happens when file restructuring leaves docs outdated; fix it by running a Python script that scans the filesystem and overwrites docs/tree.md with an up-to-date project structure tree.

Yes, you need Python installed because the automation executes a Python script located in the skills directory to traverse the filesystem and output the generated tree structure to a markdown file.

Regenerate the directory tree during file creation or repository restructuring events to refresh docs/tree.md, providing a single source of truth for onboarding and project governance audits.

The best way to maintain an accurate file tree is using an automated script that syncs the filesystem to docs/tree.md on every refactor, eliminating manual updates and providing a repeatable audit workflow.

Yes, you can use this filesystem sync approach for large refactoring cleanup; it serves as a repeatable maintenance workflow that ensures documentation accurately reflects structural changes during major file reorganizations.