10x-health-check

To check agent readiness for an existing codebase, audit dependency security, verify test infrastructure, and evaluate CI/CD configuration completeness. This generates a structured health-check report with a prioritized fix list and an overall health verdict for brownfield agent onboarding.

Auditing dependency vulnerabilities across language families involves detecting project markers like package.json, Cargo.toml, or pyproject.toml, checking for missing lockfiles, and flagging outdated dependencies with major version gaps to ensure comprehensive project health.

Yes, you can verify test runner execution readiness by detecting the test runner from common config files. The check confirms whether tests can execute successfully or reports the specific reasons why they cannot run.

Yes, CI/CD coverage evaluation checks whether lint, test, build, type, and security stages are present in the pipeline. It also identifies missing developer configuration that would hinder consistent agent contributions to the project.

Project health checks require standard project markers to be present, such as package.json, Cargo.toml, pyproject.toml, go.mod, Gemfile, composer.json, or pubspec.yaml, ensuring the tool works across common language families to assess agent readiness.

A test readiness check reports that tests cannot execute when it detects configuration gaps or missing dependencies from your common config files. It verifies the test runner and explicitly reports the underlying reasons preventing execution.