lint-and-validate

Run configured linters and type-checkers for Node.js/TypeScript and Python projects.

1|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/fnsalinas/fnsalinas.github.io --skill lint-and-validate-fnsalinas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/fnsalinas/fnsalinas.github.io/tree/main/.agent/skills/lint-and-validate
Command: npx skills add https://github.com/fnsalinas/fnsalinas.github.io --skill lint-and-validate-fnsalinas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates code quality checks to catch syntax, style, and type issues after every change.

Core Features & Use Cases

  • Automated linting and static analysis across Node.js/TypeScript and Python projects to prevent regressions.
  • Deterministic validation workflows that run npm lint/tsc or Ruff/MyPy depending on the project, in CI or pre-commit contexts.
  • Clear, per-tool results with enforced pass/fail gating to ensure codebase quality before merging.

Quick Start

Run the lint and validation workflow after every code change to ensure syntax correctness and project standards.

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

Automated linting and type checking detects your project type to run configured linters like Ruff, MyPy, eslint, and tsc. This enforces code quality by catching syntax, style, and type issues after every change.

Can I run static analysis as a pre-commit validation gate across multiple languages?

Yes, you can run static analysis in pre-commit or CI contexts to validate Node.js/TypeScript and Python projects. It provides deterministic validation workflows with clear per-tool results and a strict pass/fail gate before merging.

What static analysis tools are used to validate code quality automatically?

The validation process runs npm lint, tsc, eslint for Node.js/TypeScript, and Ruff or MyPy for Python. It detects your project type automatically and applies the appropriate configured linters to report issues.

Does the automated validation workflow support dependency auditing alongside linting?

Yes, the automated validation workflow supports dependency auditing alongside linting and type checking. It audits dependencies across languages to prevent regressions and ensure overall codebase quality before merging.

How do I enforce strict pass/fail gating for CI code quality checks?

You enforce strict pass/fail gating by running the validation workflow after code changes. It reports per-tool linting and type checking results, failing the gate if syntax, style, or type issues are detected.

Why run lint and validation checks after every code change?

Running lint and validation after every change prevents regressions by immediately catching syntax, style, and type issues. This deterministic workflow ensures codebase quality standards are met before merging to main branches.