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.
Installs into .claude/skills of the current project.
Are you the author of Lint Typecheck?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-lint-typecheck)
---
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:
```bash
cd frontend && npm run lint
```
2. Run TypeScript compilation check (no emit):
```bash
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
