Lint and Type Checking

Runs ESLint and TypeScript type checking on the frontend codebase. Use it after making code changes or before commits to catch lint warnings and type errors. Automatically lists issues with file locations and can apply ESLint auto-fixes with confirmation.

Sby Skills Guide Bot
TestingBeginner
8802/28/2026
Claude CodeCursorWindsurfCopilot
#eslint#typescript#code-quality#frontend#automation

Recommended for


name: lint-typecheck description: 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. allowed-tools: Bash, Read

Lint and Type Check

Instructions

  1. Navigate to frontend directory and run lint:

    cd frontend && npm run lint
    
  2. Run TypeScript compilation check (no emit):

    cd frontend && npx tsc -b --noEmit
    
  3. If errors are found:

    • List all errors with file locations
    • Offer to fix auto-fixable ESLint issues: npm run lint -- --fix
    • For TypeScript errors, identify the type mismatches
  4. Report summary: X lint warnings, Y lint errors, Z type errors

Examples

  • "Run lint on the frontend"
  • "Check for type errors"
  • "Validate code before commit"

Guardrails

  • Run in read-only mode first; only apply --fix with user confirmation
  • Do not modify tsconfig.json to suppress errors
  • Report all issues before attempting fixes
Related skills