lint-and-validate

To enforce linting and type checking after code changes, the Skill runs ESLint and tsc --noEmit for Node.js/TypeScript projects, and Ruff and mypy for Python projects, producing a deterministic pass/fail outcome.

Automating static analysis and type validation is best handled by running Ruff and mypy for Python, alongside ESLint and tsc for TypeScript, which enforces code quality and type safety to prevent regressions and standard violations after each code change.

Yes, static analysis and type validation works with both Python and Node.js projects. It runs Ruff and mypy for Python code, and ESLint and tsc --noEmit for TypeScript, ensuring consistent code style and type safety across both ecosystems.

Yes, security auditing can run alongside linting and type checking via npm audit where applicable. This surfaces high-severity dependency risks while simultaneously enforcing code style with ESLint and type safety with tsc or mypy.

Static type validation prevents runtime failures by running tsc --noEmit for TypeScript and mypy for Python after code changes. This process catches type mismatches before deployment, enforcing type safety and reducing runtime errors caused by incorrect type usage.

No, Trunk is optional and runs if available, but the core linting and static checks run using standard tools like ESLint, tsc, Ruff, and mypy. You only need the standard linting and type checking tools configured in your Node.js or Python project.