Search

PythonReactSEOPDF
GitHub Skill

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.

aiskillstore☆ 123 Repository stars6 Repository forks

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

View source ↗Guides

Skill instructions

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

Examples

Read the usage examples in the source repository.

View source ↗

Source history

Indexed on
2026-01-20
Index updated
2026-01-28
Branch
main

Index and sync dates describe this directory. View the source repository for code history.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!