lint-and-validate

Automate linting and type checks by running a skill that executes static analysis across Node.js and Python projects to catch regressions and fix issues where possible. It performs type checking and security audits as part of the quality loop after every modification.

Yes, existing project configurations for ESLint, TSConfig, ruff, or mypy are required to run automated code validation. The skill relies on these present configurations to perform linting, type checks, and security audits, requiring reports to be reviewed before submission.

The best way to catch regressions before review is to run automated linting and type checks after every commit. This quality loop performs static analysis and security audits on Node.js and Python changes, producing consistent, error-free builds and safer code.

Static analysis checks for code quality, type errors, and security vulnerabilities in TypeScript and Python codebases. It runs linting to fix issues where possible and performs type checks to ensure consistent, error-free builds after every modification.

Yes, you can run type checking and security audits together after modifying code. The skill automates quality control by combining linting, type checks, and security validation into a single loop for Node.js/TypeScript and Python projects.

Automated linting requires existing project configurations because the skill leverages your established ESLint, TSConfig, ruff, or mypy rulesets to execute static analysis. Without these present configurations, the validation process cannot accurately assess or fix code quality issues.