lint-and-validate
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.
Best use case
lint-and-validate is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 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.
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.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "lint-and-validate" skill to help with this workflow task. Context: 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.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lint-and-validate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lint-and-validate Compares
| Feature / Agent | lint-and-validate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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>` |
Related Skills
lint-fixer
Use this skill to run npm run lint and fix linting issues. Triggers on fixing lint errors after code changes or validating code against project style guidelines.
deployment-validation-config-validate
You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat
azure-validate
Pre-deployment validation checkpoint. Run deep checks to ensure your application is ready for Azure deployment. Validates configuration, infrastructure, permissions, and prerequisites. USE FOR: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors. DO NOT USE FOR: creating or building apps (use azure-prepare), executing deployments (use azure-deploy).
lint
How to lint and typecheck in this project. Load when implementing or verifying code.
run-linters
Run linters after code changes to verify code quality. Use this skill after completing code modifications to catch and fix any linting issues.
lint-typecheck
Run ESLint and TypeScript type checking on the frontend codebase. Use when user mentions "lint", "type check", "check code", "eslint", "tsc", or before committing changes.
lint-dotnet
Run .NET architecture linter to check for MSBuild/CPM violations
container-hadolint
Dockerfile security linting and best practice validation using Hadolint with 100+ built-in rules aligned to CIS Docker Benchmark. Use when: (1) Analyzing Dockerfiles for security misconfigurations and anti-patterns, (2) Enforcing container image security best practices in CI/CD pipelines, (3) Detecting hardcoded secrets and credentials in container builds, (4) Validating compliance with CIS Docker Benchmark requirements, (5) Integrating shift-left container security into developer workflows, (6) Providing remediation guidance for insecure Dockerfile instructions.
validate-requirements
Validate that input meets prerequisites based on the user's saved standards for the project type. Use at the start of any quality pipeline to ensure the user has provided sufficient requirements.
html-structure-validate
Validate HTML5 structure and basic syntax. BLOCKING quality gate - stops pipeline if validation fails. Ensures deterministic output quality.
firebase-development-validate
This skill should be used when reviewing Firebase code against security model and best practices. Triggers on "review firebase", "check firebase", "validate", "audit firebase", "security review", "look at firebase code". Validates configuration, rules, architecture, and security.
css-development-validate
This skill should be used when reviewing or auditing existing CSS code for consistency with established patterns. Triggers on "review CSS", "audit styles", "check CSS", "validate stylesheet", "CSS review". Checks semantic naming, dark mode coverage, Tailwind usage, and test coverage.