meow:lint-and-validate

Lint and validate Node.js/TypeScript and Python code with ESLint, Ruff, and MyPy.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-lint-and-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meow:lint-and-validate
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Alint-and-validate
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-lint-and-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (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 and type-checking across Node.js/TypeScript and Python projects.
  • Runs project-specific validation scripts to enforce MeowKit standards.
  • Use Case: Before committing, run the lint-and-validate skill to catch syntax, style, and type errors early.

Quick Start

Run the lint-and-validate workflow after every change to ensure a clean build.

Frequently Asked Questions about meow:lint-and-validate

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

FAQPage Schema
How do I run lint and type checks across TypeScript and Python projects?

To lint and type-check mixed TypeScript and Python projects, you can run a validation workflow that executes ESLint and TypeScript checks for Node.js, alongside Ruff and MyPy for Python, to enforce syntax correctness and project standards.

Can I use static analysis to enforce code quality before committing changes?

Yes, you can run static analysis and linting as a pre-commit check. This validates code modifications against project standards, catching syntax, style, and type errors early before changes are committed to version control.

What is the best way to catch syntax and type errors early in a CI pipeline?

The best way to catch errors early in a CI pipeline is to run automated lint and validation scripts. This performs static analysis on every code change to ensure syntax correctness and enforce project rules continuously.

Does this validation workflow support both Node.js and Python environments?

Yes, this validation workflow supports both Node.js and Python environments. It implements ESLint and TypeScript checks for Node.js, and runs Ruff and MyPy static analysis for Python projects.

Why should I run code validation after every modification during local development?

Running code validation after every modification during local development ensures a clean build by catching syntax, style, and type errors immediately. This prevents issues from accumulating and failing later in CI pipelines.

How do project-specific validation scripts enforce custom rules in a codebase?

Project-specific validation scripts enforce custom rules by running targeted static analysis checks. These scripts validate code against MeowKit standards, ensuring that all modifications adhere to the defined project rules and formatting requirements.