ln-622-build-auditor

Run a build audit to detect compiler errors, linter issues, type mismatches, and failed tests before merging. This verifies code quality and flags build configuration issues, providing actionable recommendations with severity and estimated effort to prevent broken builds.

A code quality audit checks for compiler and linter errors, deprecation warnings, type mismatches, and failed automated tests. It also inspects build configuration issues, reporting findings with severity, location, and estimated resolution effort to ensure higher code quality.

Yes, build auditing provides actionable recommendations for resolving linter warnings and type errors. Findings include severity, exact location, and estimated development effort, allowing you to proactively prioritize and resolve code quality issues efficiently.

You should run a build configuration audit before merging new features or deploying changes. This proactively catches deprecation warnings, type errors, and configuration problems, ensuring automated tests pass and preventing runtime errors in production.

Yes, build auditing specifically validates automated tests and catches deprecation warnings alongside compiler and type errors. It ensures your build process maintains high code quality and verifies that all test suites are passing before integration.