script-ecosystem-audit

To run a script infrastructure health audit, execute the audit process to analyze your entire /scripts/ directory. It evaluates module consistency, safety, registration, code quality, and testing, then outputs a structured JSON report containing findings, category scores, and patch suggestions.

A script infrastructure health check evaluates module systems, safety, registration, code quality, and testing domains. It assigns per-category scores and a composite health grade to surface invisible risks and identify issues before they impact development velocity.

Yes, you can track script health trends through state persistence and baseline comparison. The audit maintains a historical state log, enabling trend analysis and regression detection across multiple runs to monitor evolving health risks.

The script ecosystem audit outputs a v2 JSON payload. This structured format includes detailed findings, category scores, historical trends, and actionable patch suggestions for identified code issues.

You should use an automated script health audit when your repository's script ecosystem grows complex and risks becoming invisible. It proactively surfaces module and testing issues before they impact development velocity.

The audit applies specifically to the /scripts/ ecosystem. While it comprehensively scores module consistency, safety, registration, code quality, and testing, it does not evaluate code outside this directory structure.