lint-and-validate

To run lint and type checks after code changes, execute the lint_runner.py script against your project. It detects the project type, applies the appropriate validation tools, and reports per-tool results to guide necessary fixes.

Static analysis supports both Python and TypeScript projects. The tool detects the ecosystem by identifying Node.js or Python code and automatically applies the relevant linters, tsc, and Python type-checking tools to validate the repository.

To standardize code quality gates across repositories, use the reusable lint_runner.py and type_coverage.py scripts. They provide a repeatable loop for linting, type checking, and security checks with clear success or fail signals.

To get structured results from linting and type checking, run the validation loop to execute the detected tools with defined commands. The process exports a structured result JSON detailing per-tool outcomes to guide your fixes.

Post-change validation is needed because IDE checks may miss repository-wide issues. Running a dedicated validation loop ensures all changes pass linting, type checking, and security scans before work is considered complete, reducing defects.

You can use lint-and-validate without external Skill dependencies, but the target project must contain its own linters and type-checking tools. The script detects these existing tools to execute the validation commands.