Lint and validate

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/lint-and-validate

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill lint-and-validate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.1 KB, as published. Nobody here has run it

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

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

Python

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

The Quality Loop

Write/Edit Code
Run Audit for the project's ecosystem:
- Node.js / TypeScript: npm run lint && npx tsc --noEmit
- Python: ruff check . --fix && mypy . && bandit -r . -ll
Analyze Report: Check the "FINAL AUDIT REPORT" section.
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.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.