verify

Automated project health verification detects the technology stack from config files and sequentially runs type-check, tests, and build checks. It supports Node.js, Python, Go, and Rust repositories to ensure quality gates stay green after code changes.

Yes, automated verification works with Node.js, Python, Go, and Rust projects. It detects the project type from common configuration files and executes the appropriate sequence of type-check, test, and build commands for the detected stack.

Run a single verification command after modifying code to validate the full quality gate. It automatically detects the stack and produces a concise summary table of type-check, test, and build results with readable failure reporting for any issues found.

Post-change validation executes checks sequentially and provides readable failure reporting. It displays a concise summary table of overall results while showing specific failure details when type-check, test, or build issues occur, all without modifying files.

Yes, lint checks run alongside type-check, tests, and builds when available. The verification sequence automatically includes linting in the quality gate validation for supported repositories, adding it to the concise summary table report.

No, automated quality gates operate with read-only behavior and do not modify any project files. The verification process only runs type-check, tests, and build checks sequentially to report health status without altering the repository.