lint-and-validate

Automates linting and static analysis for Node.js/TypeScript and Python projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill reduces manual QA by automatically running linting, formatting, and static analysis after each code change to ensure syntax correctness and adherence to project standards.

Core Features & Use Cases

  • Linting and auto-fix across Node.js/TypeScript and Python projects to catch style and correctness issues early.
  • Type checking and static analysis using available tools (tsc, ruff, mypy) to enforce correct typing and reduce runtime errors.
  • Security and quality gates, including automated audits, to prevent known issues from slipping into code reviews.

Quick Start

Run the lint-and-validate skill after every code change to automatically lint, type-check, and audit the project.

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 static analysis after code changes?

Automating linting and static analysis after code changes is done by running checks that execute configured linters to validate syntax, style, and type correctness, halting progress until issues are resolved.

What is the best way to run type checking for TypeScript and Python projects?

Type checking for TypeScript and Python projects is best handled by running static analysis tools like tsc, ruff, and mypy to enforce correct typing and reduce runtime errors after every code modification.

Does automated code quality control work with both Node.js and Python ecosystems?

Automated code quality control works with Node.js and Python ecosystems by applying configured linters and static analysis tools to catch style and correctness issues across multiple project types.

Can I halt progress when linting fails to prevent issues from slipping into code reviews?

Halting progress when linting fails prevents issues from slipping into code reviews by executing configured linters and reporting failures immediately, ensuring syntax correctness and adherence to project standards.

Why do I need automated security and quality gates for my code?

Automated security and quality gates are needed to prevent known issues from slipping into code reviews by running automated audits and static analysis after each code change to ensure syntax correctness.