.agent/skills/lint-and-validate/SKILL.md
--- name: lint-and-validate description: 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. allowed-tools: Read, Glob, Grep, Bash --- # 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 ###
npx skillsauth add CongDon1207/AGENTS.md .agent/skills/lint-and-validateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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> |
development
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications, OR when they provide screenshots/images/designs to replicate or draw inspiration from. For screenshot inputs, extracts design guidelines first using ai-multimodal analysis, then implements code following those guidelines. Generates creative, polished code that avoids generic AI aesthetics.
development
Use when the user asks to investigate, understand, explore, or explain how a feature works, asks about existing logic, or wants to understand code flow. Triggers on keywords like "how does", "explain", "investigate", "understand", "what does", "where is", "how works", "logic flow", "trace", "explore feature".
development
Use when the user asks to implement a new feature, enhancement, add functionality, build something new, or create new capabilities. Triggers on keywords like "implement", "add feature", "build", "create new", "develop", "enhancement".
development
Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".