lint-and-validate

Run configured linting and type-check tools for Node.js/TypeScript and Python projects.

Updated Sep 2, 2025
One-click install
npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill lint-and-validate-rafaelminatto1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/rafaelminatto1/fisioflow-51658291/tree/main/.agent/skills/lint-and-validate
Command: npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill lint-and-validate-rafaelminatto1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.

Core Features & Use Cases

  • Linting and static analysis to catch syntax errors, style issues, and potential bugs.
  • Cross-language checks for Node.js/TypeScript and Python projects with type validation.
  • Automated validation after code changes to maintain code health and reliability.

Quick Start

Run the lint_runner.py script against your project to execute all configured lint and type-check tools.

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 for Node.js and Python projects?

You can automate linting and type checking by running a coordinating lint runner script that orchestrates configured tools like eslint, tsc, Ruff, and MyPy to validate syntax and project standards across Node.js and Python projects.

What is static analysis for code correctness and when do I need it?

Static analysis for code correctness is the automated validation of syntax, types, and security before commits. You need it after every code modification to catch errors, style issues, and potential bugs to maintain code health.

Do I need to configure eslint and MyPy before running automated validation?

Yes, you need project-configured tooling such as eslint and tsc for Node.js or Ruff and MyPy for Python. The automation requires these tools to be pre-configured to orchestrate checks and report results accurately.

Can I use one script to run cross-language static analysis checks?

Yes, you can run a single lint runner script to execute cross-language checks. It applies unified linting and type validation to both Node.js/TypeScript and Python projects to ensure code correctness.

What is the best way to catch potential bugs before committing code changes?

The best way to catch potential bugs before committing is to trigger automated lint and static analysis procedures after code modifications. This validates syntax correctness and project standards to ensure code reliability.