source-command-validate

Comprehensive code validation executes a structured flow combining linting, type checking, formatting, testing, and build checks. Issuing the validate command runs these automated validation steps sequentially across the entire codebase.

Full codebase health validation includes linters, type checkers, formatters, test suites, build checks, and end-to-end tests. It operates through a layered pyramid model, starting with basic linting and progressing to complex test suites.

Yes, layered validation allows step-by-step execution through a pyramid model. You can progress sequentially from linters to type checkers, formatters, and finally build and test suites, rather than running everything simultaneously.

Automated code validation generates a detailed report listing all validation statuses and identified issues. The report provides specific status updates for each validation step along with recommended fixes for the discovered problems.

No external dependencies are required to run continuous integration code validation. The skill operates independently using internal scripts to execute linters, type checkers, formatters, and tests without needing external packages.

The best way to check code health before a release is running a full-featured validation flow. This combines linting, type checking, formatting, and testing into a single structured process that produces a detailed status report with recommended fixes.