lint-and-validate

xenitV1's avatarfrom xenitV1

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.

⭐62stars🔀15forks📁View on GitHub🕐Updated Jan 2, 2026⬇️3downloads

When & Why to Use This Skill

The Lint and Validate skill automates essential quality control procedures, including linting, static analysis, and type checking. Designed for modern development workflows, it ensures code correctness and adherence to project standards across Node.js, TypeScript, and Python environments by enforcing a strict 'Quality Loop' after every modification, effectively reducing technical debt and preventing runtime errors.

Use Cases

  • Automated Code Linting: Instantly identify and fix stylistic and syntax issues using tools like ESLint and Ruff to maintain a clean and consistent codebase.
  • Static Type Analysis: Prevent complex runtime bugs by performing rigorous type checking with TypeScript (tsc) and MyPy during the development process.
  • Security Vulnerability Scanning: Proactively detect high-level security risks in project dependencies and source code using integrated tools like npm audit and Bandit.
  • Standardized Development Workflow: Implement a mandatory validation step that ensures no code is committed or marked as complete without passing predefined quality benchmarks.
namelint-and-validate
descriptionAutomatic 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.
allowed-toolsRead, Glob, Grep, Bash

Lint and Validate Skill

MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

Procedures by Ecosystem

Node.js / TypeScript

  1. Lint/Fix: npm run lint or npx eslint "path" --fix
  2. Types: npx tsc --noEmit
  3. Security: npm audit --audit-level=high

Python

  1. Linter (Ruff): ruff check "path" --fix (Fast & Modern)
  2. Security (Bandit): bandit -r "path" -ll
  3. Types (MyPy): mypy "path"

The Quality Loop

  1. Write/Edit Code
  2. Run Audit: npm run lint && npx tsc --noEmit
  3. Analyze Report: Check the "FINAL AUDIT REPORT" section.
  4. Fix & Repeat: Submitting code with "FINAL AUDIT" failures is NOT allowed.

Error Handling

  • If lint fails: Fix the style or syntax issues immediately.
  • If tsc fails: Correct type mismatches before proceeding.
  • If no tool is configured: Check the project root for .eslintrc, tsconfig.json, pyproject.toml and suggest creating one.

Strict Rule: No code should be committed or reported as "done" without passing these checks.


Scripts

Script Purpose Command
scripts/lint_runner.py Unified lint check python scripts/lint_runner.py <project_path>
scripts/type_coverage.py Type coverage analysis python scripts/type_coverage.py <project_path>