// Automatic quality control, linting, and static analysis procedures. Use when validating code changes for syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.
Refactoring and cleanup - improving code structure, removing dead code, eliminating duplication, or pre-merge cleanup. Use when code is hard to maintain, has dead code or debug artifacts, or needs pre-merge polishing.
Fix a GitHub issue end-to-end - from reading the issue, understanding requirements, implementing the fix, writing tests, and creating a commit. Use when given a GitHub issue number or URL to resolve.
Optimize code for readability, performance, maintainability, and security across Bash, Python, and Rust. Use when asked to improve code quality, optimize performance, add type safety, or refactor for idioms.
Create, debug, and optimize GitHub Actions workflows with security best practices. Use when asked to "create workflow", "fix workflow", "add CI", or needs help with GitHub Actions.
Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes.
Craft immersive, high-performance premium web experiences with advanced motion, typography, and architectural craftsmanship. Use when building award-level landing pages, interactive portfolios, or components requiring top-tier visual polish.
| name | lint-and-validate |
| description | Automatic quality control, linting, and static analysis procedures. Use when validating code changes for syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis. |
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 skills/lint-and-validate/scripts/lint_runner.py <project_path> |
| scripts/type_coverage.py | Type coverage analysis | python skills/lint-and-validate/scripts/type_coverage.py <project_path> |