script-auditor

You can enforce script quality by running an audit on tracked git files to check for required documentation, validate language choices, and verify the presence of help commands and status indicators.

The best way to check for missing documentation is to audit the scripts against a standard that requires general notes, usage instructions, output descriptions, and version history, generating a compliance report for the repository.

Yes, you need Node.js version 24 or higher to execute the automated auditing logic against tracked git files and generate a compliance report for your helper scripts.

No, Python is flagged as a banned technology during the audit; the policy enforcement encourages using modern Node.js ES modules or zsh instead to maintain repository standards.

Auditing language choice and status emojis ensures scripts avoid banned technologies like Python, remain maintainable with modern Node.js or zsh, and provide user-friendly indicators for quick visual health checks.

You should run a script standards audit when adding a new utility to the repository to ensure it meets project guidelines, or periodically as a health check to identify and fix drift in existing tooling.