Skills Guide

Lint and Validate

VerifiedSafe

Automatic quality control, linting, and static analysis for Node.js and Python projects. Ensures code is error-free before committing.

Download and use
Sby Skills Guide Bot
TestingBeginner
7/24/2026
Claude CodeCursorCodex
#linting#static-analysis#code-quality#typescript#python

Recommended for

Backend developerClaude CodeTest generationCursorFullstack developerCodex

Automated summary

Runs linting, type checking, and security audits for Node/TypeScript and Python projects after each code change, enforcing a fix-and-repeat loop until checks are clean.

Strengths

  • Covers two ecosystems with concrete commands (ESLint/tsc, Ruff/mypy)
  • Includes security checks through npm audit and Bandit
  • Requires re-running checks until everything passes
  • Ships helper scripts for unified lint and type coverage analysis

Limitations

  • Only covers Node/TypeScript and Python ecosystems
  • Assumes the project already has its tooling configured
  • Security analysis is shallow (dependency audit and Bandit), not full SAST
When to use it

Use after editing code when you want a quick pass over lint, types, and security before declaring the work done.

When not to use it

Skip it for projects outside JavaScript/TypeScript or Python, or when no tooling is configured and you don't want the skill to scaffold it.

Security analysis

Safe
Quality score80/100

The skill instructs running standard linting, type-checking, and security auditing commands (eslint, tsc, npm audit, ruff, bandit, mypy) via Bash. These are legitimate development quality-control actions with no destructive, exfiltrating, or obfuscated behavior.

No concerns found

How this analysis is made

Examples

Fix lint after refactor
I just refactored the auth module in src/auth — run the linter and TypeScript checks and fix anything that fails.
Python quality pass
Run Ruff, Bandit, and MyPy on the payments service and summarize the remaining issues.
Pre-commit validation
Validate my changes before I commit: run linting, type checking, and dependency security audits, and fix the problems you find.

name: lint-and-validate description: "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, v..." allowed-tools: Read, Glob, Grep, Bash risk: unknown source: community

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> |

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/lint-and-validate-mryiqgvx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/lint-and-validate-mryiqgvx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/lint-and-validate-mryiqgvx/download' --output '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md.part' && mv '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md.part' '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Glob, Grep, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md' && test -s '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/lint-and-validate' && cp -R '.skill-downloads/lint-and-validate-mryiqgvx' '.claude/skills/lint-and-validate'

Cursor
test -f '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md' && test -s '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/lint-and-validate' && cp -R '.skill-downloads/lint-and-validate-mryiqgvx' '.cursor/skills/lint-and-validate'

Codex
test -f '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md' && test -s '.skill-downloads/lint-and-validate-mryiqgvx/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/lint-and-validate' && cp -R '.skill-downloads/lint-and-validate-mryiqgvx' '.agents/skills/lint-and-validate'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/lint-and-validate-mryiqgvx'

openskills read 'lint-and-validate-mryiqgvx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/lint-and-validate-mryiqgvx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

ClickHouse Performance Comparison

Testing

Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.

Claude CodeintermediateSafe 49,547
Skills Guide Bot

Analyze CI Performance Reports

Testing

Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.

Claude CodeintermediateSafe 49,516
Skills Guide Bot

Santa Method

Testing

Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.

Claude CodeCodexCursorintermediateSafe 244,766
Skills Guide Bot