lint-and-validate

Run eslint/tsc and ruff/mypy checks after every code change.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/BenWork17/VeXeViet --skill lint-and-validate-benwork17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/BenWork17/VeXeViet/tree/main/.agent/skills/lint-and-validate
Command: npx skills add https://github.com/BenWork17/VeXeViet --skill lint-and-validate-benwork17

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatic quality control by running linting, type checking, and static analysis after every code modification to prevent syntax errors and style issues.

Core Features & Use Cases

  • Unified validation across Node.js/TypeScript and Python projects using established tools (eslint/tsc and ruff/mypy).
  • Immediate feedback on code changes, ensuring quick fixes before commits.
  • Use Case: A development team can integrate this skill into their CI pipeline to fail builds when lint or type checks fail.

Quick Start

Run the lint-and-validate workflow after every code change to ensure syntax correctness and standards compliance.

Frequently Asked Questions about lint-and-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate linting and type checking after every code change?

Automate linting and type checking by running a validation workflow after every code modification to identify and fix code quality issues. This provides immediate feedback on syntax errors and style issues, ensuring quick fixes before commits.

Can I run eslint and tsc static analysis checks for both Node.js and Python projects?

Yes, you can run static analysis checks for both Node.js/TypeScript and Python projects. The validation workflow covers eslint/tsc and ruff/mypy workflows using configurable scripts to enforce code quality across different languages.

What do I need to set up before running ruff and mypy static analysis on my Python code?

You need explicit tooling presence before running ruff and mypy static analysis. Ensure your Python project has the necessary ruff and mypy configuration files, along with the required lint scripts defined, so the validation workflow can execute successfully.

Does static analysis fail the CI pipeline build when lint or type checks fail?

Yes, static analysis fails the CI pipeline build when lint or type checks fail. The workflow reports failures to prevent commits until issues are resolved, ensuring that only code passing syntax correctness and standards compliance is merged.

What is the best way to prevent syntax errors and style issues before committing code?

The best way to prevent syntax errors and style issues is unified validation across your projects. By running lint, type checking, and static analysis after every code modification, you get immediate feedback and ensure standards compliance before committing.

Why does my lint-and-validate workflow not run properly without a tsconfig or ruff config?

The lint-and-validate workflow does not run properly without a tsconfig or ruff config because it requires explicit tooling presence. Without these configuration files and defined lint scripts, the validation engine cannot execute the necessary static checks.