Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 43% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 50% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 76% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -10% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 26% | 0% |
> 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> |
Other measured skills in the registry, with their headline benchmark lift.