lint-and-validate

Run linters, type checkers, and security audits for Node.js/TypeScript and Python projects.

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

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 across Node.js/TypeScript and Python projects to catch syntax errors and enforce style.
  • Type checking and security audits to prevent runtime issues and vulnerabilities.
  • Use in CI, pre-commit, or local development to maintain consistent code quality across teams.

Quick Start

Run the unified lint and validation workflow after each code change to ensure a clean, compliant codebase.

Frequently Asked Questions about lint-and-validate

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

FAQPage Schema
How do I run linting and type checking after making code changes?

You can automate linting and type checking by running a unified validation workflow after each code modification. This executes linters and type checkers like eslint and tsc to ensure syntax correctness and project standards.

Can I run static analysis and security audits locally or in CI for Python and Node.js?

Static analysis and security audits work across Node.js/TypeScript and Python projects in CI, pre-commit, or local development. They use tools like Ruff and Mypy to catch vulnerabilities and maintain consistent code quality.

What tools do I need for automated code quality assurance in TypeScript and Python?

Automated code quality assurance requires tooling like eslint and tsc for Node.js/TypeScript, and Ruff and Mypy for Python. These tools execute the linting, type checking, and security audits.

Does running linters and type checkers provide a pass or fail audit report?

Running linters and type checkers surfaces a final pass or fail audit with a consolidated report. This validates syntax correctness and adherence to project standards after every code change.

When should I use automated static analysis instead of manual code review?

Automated static analysis should be used after every code modification to instantly catch syntax errors and enforce style. It acts in CI, pre-commit, or local development to ensure consistent quality before manual review.

Why does my code validation fail after running linters and type checkers across different environments?

Code validation fails when linters and type checkers detect syntax errors or standard violations. The consolidated audit report identifies these issues across Node.js/TypeScript and Python projects to ensure correctness.