lint-and-validate

Run lint, format, and static analysis checks on Node.js/TypeScript and Python codebases.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill lint-and-validate-driveconnect-alpha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/DriveConnect-alpha/DriveConnect/tree/main/.agent/skills/lint-and-validate
Command: npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill lint-and-validate-driveconnect-alpha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers waste time chasing style violations, type errors, and inconsistent code quality across multi-language projects. This Skill provides a unified, automated gate that enforces coding standards after every change.

Core Features & Use Cases

  • Unified linting and type-checking across Node.js/TypeScript and Python projects using a single runner.
  • Automatic selection of appropriate tools (eslint/tsc for Node.js; ruff/mypy for Python) with consistent reporting.
  • Output-ready results for CI and audit trail, guiding quick fixes and preventing broken builds.

Quick Start

Execute the lint runner on your project path to perform automatic linting and type checks for Node.js or Python code.

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 lint and static analysis checks for both TypeScript and Python projects?

This unified lint runner automates code quality checks by executing eslint and tsc for Node.js or ruff and mypy for Python, applying strict pass criteria and returning a unified audit report to guide fixes.

What is the best way to enforce strict code quality standards across a multi-language codebase?

An automated linting gate enforces strict code quality across multi-language codebases by executing static analysis tools, detecting style violations, and automatically failing the build when issues are detected to prevent broken code.

Does this automated code check tool support CI-CD pipelines?

Yes, the automated lint runner supports CI-CD pipelines by producing output-ready results and a final audit report that guides quick fixes and prevents broken builds from entering your pipeline.

Can I use mypy and ruff for Python static analysis within a Node.js and TypeScript monorepo?

Yes, the runner accommodates multiple ecosystems by executing mypy and ruff for Python static analysis alongside eslint and tsc for Node.js, yielding a unified audit report across both languages.

Why does my automated lint runner fail the build when type errors are detected?

The automated lint runner fails the build because it enforces strict pass criteria, automatically triggering a failure when type errors or style violations are detected to prevent broken builds.