lint-and-validate

Run configured linters and type checkers for Node.js and Python projects.

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

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.

Core Features & Use Cases

  • Linting and static analysis across Node.js/TypeScript and Python projects
  • Unified validation that runs after code changes to catch issues early
  • Security and quality checks integrated into the development workflow

Quick Start

Run the unified lint runner on your project to perform checks and surface issues.

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 static analysis across Node.js and Python projects?

To run linting and static analysis across Node.js and Python, use a unified validation runner that executes configured linters and type checkers like ruff, mypy, lint, and tsc to enforce syntax correctness and project standards.

Can I use this to automate type checking and linting in CI workflows?

Yes, you can automate type checking and linting in CI workflows by running the cross-language validation runner after code modifications to catch syntax issues and enforce project standards early in the development cycle.

What static analysis tools are supported for Python and Node.js projects?

The static analysis tools supported for Python and Node.js projects include ruff and mypy for Python, alongside lint and tsc for Node.js and TypeScript, covering typical codebases and CI workflows.

How do I configure executable scripts for automated code quality checks?

To configure executable scripts for automated code quality checks, place your tools in the scripts/ directory and provide a SKILL.md frontmatter with name and description to output structured validation results.

Why does my cross-language validation fail to find executable tools?

Cross-language validation fails to find executable tools when the scripts/ directory is missing or the required SKILL.md frontmatter containing the name and description fields is not properly configured.

Do I need separate linters for Node.js and Python type checking?

No, you do not need separate linters for Node.js and Python type checking; a unified validation runner can apply both lint and tsc for Node.js alongside ruff and mypy for Python in a single workflow.