project-health

Automated project health checks verify internal consistency by comparing documented skill counts against actual files, detecting stale session files older than 30 days, and checking documentation currency against recent code changes. This process proactively identifies maintenance issues in a structured report.

Detecting stale session files and monitoring cache size involves scanning directories for session files older than 30 days and reporting the total cache directory size. The system flags old files for cleaning and suggests cache cleanup when the size exceeds a defined threshold.

Validating installation script syntax is performed as an internal integrity check during project maintenance. The system automatically verifies the syntax of installation scripts and reports any errors, ensuring deployment scripts remain functional and error-free.

Yes, the automated health check works without external dependencies. It performs internal operations including skill count verification, session file detection, cache monitoring, script validation, and documentation sync checks independently within the project environment.

You should run an internal consistency check on project documentation when maintaining project health, verifying that documented skill counts match actual files, and ensuring documentation is up-to-date with recent code changes. It is often run proactively to identify potential issues.