Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.
64
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/lint-and-validate/SKILL.mdThe canonical home for this skill is jbvc/lint-and-validate
MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.
npm run lint or npx eslint "path" --fixnpx tsc --noEmitnpm audit --audit-level=highruff check "path" --fix (Fast & Modern)bandit -r "path" -llmypy "path"npm run lint && npx tsc --noEmitlint fails: Fix the style or syntax issues immediately.tsc fails: Correct type mismatches before proceeding..eslintrc, tsconfig.json, pyproject.toml and suggest creating one.Strict Rule: No code should be committed or reported as "done" without passing these checks.
| 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> |
04514f0
Canonical home
since Mar 31, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.