lint-typecheck

AppleLamps's avatarfrom AppleLamps

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.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 28, 2025⬇️4downloads
[Testing and QA]

When & Why to Use This Skill

This Claude skill automates frontend code quality assurance by performing comprehensive ESLint and TypeScript type checking. It streamlines the development workflow by identifying syntax errors, style violations, and type mismatches, providing developers with actionable reports and the ability to automatically fix linting issues to maintain a clean, production-ready codebase.

Use Cases

  • Pre-commit Validation: Use the skill to verify code integrity before committing changes, ensuring that no linting errors or type mismatches are introduced into the repository.
  • Automated Code Audits: Quickly scan large frontend codebases to identify technical debt, inconsistent coding styles, or hidden type errors that could lead to runtime failures.
  • Refactoring Support: After making significant changes to shared types or components, run the type checker to instantly locate and resolve all downstream type mismatches across the project.
  • Continuous Quality Monitoring: Integrate as a standard check during the development process to provide real-time feedback on code health and adherence to project-specific linting rules.
namelint-typecheck
descriptionRun 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-toolsBash, 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