system-maintenance

To keep documentation in sync after structural changes, you audit and verify configuration files against the actual system state. This process identifies discrepancies and automatically applies corrections to ensure consistency across artifact types and component listings.

The best way to audit system configuration files is to run an automated verification process that compares documentation against the current system state. It checks for consistency in artifact types, stage gates, and component listings, reporting any inconsistencies found.

You can automatically update CLAUDE.md and SETUP.md files by running a synchronization process that verifies documentation against current system configurations. It applies necessary automated corrections, ensuring documentation accurately reflects any newly added skills or tools.

Yes, the documentation audit works without external dependencies. It operates independently using internal scripts and references to verify system state and apply automated fixes to documentation files.

You need to run a system documentation sync after making structural changes to skills, agents, or tools. This ensures configuration files and setup documentation accurately reflect the current system state and maintain consistency across artifact types.

System documentation shows incorrect component listings when it is not synchronized after structural changes. Running an automated audit verifies documentation against the actual system state and applies corrections to resolve these inconsistencies.