lint-and-validate

Static analysis detects syntax, style, and type errors in TypeScript and Python projects by running tools like ESLint, MyPy, and Ruff. This automated post-change validation prevents broken code from slipping through by enforcing linting and type safety rules across your repository.

Yes, you can validate both Node.js and Python repositories. The skill supports multi-ecosystem workflows by detecting your project type and applying ecosystem-appropriate tools, automatically running TypeScript compiler checks or Python static analysis like Ruff and MyPy based on your environment.

To run automated post-change verification for type safety, you need available project scripts or local tooling such as ESLint, the TypeScript compiler, Ruff, or MyPy. These dependencies must be configured in your environment to enable syntax, style, and type coverage checks.

To fix static analysis errors, review the summarized validation results which provide concise guidance on caught lint, type, and style failures. You then correct the flagged syntax or type issues in your code and rerun the deterministic helper scripts to verify the fixes.

You should avoid running automated static validation checks when your project lacks the required local tooling or scripts. Without ecosystem-appropriate tools like ESLint, TypeScript compiler, Ruff, or MyPy configured, the validation process cannot confirm syntax, style, and type safety.