Our review
Runs TypeScript type-check and ESLint, then automatically fixes any errors found, following strict guidelines to delete unused code.
Strengths
- Automates fixing type and lint errors
- Enforces deletion of unused code (no underscore prefixing)
- Fix-and-check cycle until clean pass
- Respects project architecture and type safety
Limitations
- Requires a preconfigured npm run check command
- May introduce unwanted changes if error analysis is misinterpreted
- Does not handle business logic or test failures
When you need to validate and clean TypeScript code quality before a commit, PR, or deployment.
When the project lacks a check script or you intentionally want to keep unused code.
Security analysis
SafeThe skill instructs running 'npm run check' (a local development script) and using the Edit tool to fix found errors. No destructive or exfiltrating actions are involved, and no network requests or external scripts are executed. It is a standard code-quality maintenance task.
No concerns found
Examples
Run the check command to find and fix all TypeScript and ESLint errors in the project. Make sure to delete any unused imports, variables, or parameters instead of prefixing them with underscores.Run TypeScript type-check and ESLint on src/components/Button.tsx, then fix any errors found.name: check description: Run TypeScript type-check and ESLint, then fix any errors found. Use when you need to validate code quality or fix linting issues.
TypeScript and ESLint Check & Fix
Run TypeScript type-check and ESLint, then fix any errors found.
Instructions
-
Run the check command:
- Execute
npm run checkto run both TypeScript type-check and ESLint - Capture and analyze all errors and warnings
- Execute
-
If errors are found:
- Analyze each error carefully before making changes
- Fix TypeScript errors:
- Resolve type mismatches
- Add missing type annotations
- Fix import/export issues
- Ensure proper null/undefined handling
- Fix ESLint errors:
- CRITICAL: For
no-unused-varserrors, DELETE unused code completely - DO NOT prefix variables with underscores - remove them instead
- Fix import order and formatting issues
- Resolve any other ESLint rule violations
- CRITICAL: For
- Use appropriate tools:
- Use
Edittool for file changes (not bash sed/awk) - Use
Readtool to examine files before editing - Make targeted, precise fixes
- Use
-
Re-run the check:
- After fixing errors, run
npm run checkagain - Verify all errors are resolved
- After fixing errors, run
-
Repeat until clean:
- Continue the fix-and-check cycle until
npm run checkpasses without errors - Report the final status
- Continue the fix-and-check cycle until
Project-Specific Guidelines
- Unused Code Policy: DELETE unused imports, variables, and parameters - don't prefix with underscores
- Architecture: Follow
/src/directory structure with features, components, lib separation - Type Safety: Maintain proper TypeScript types throughout
- Code Quality: Ensure all fixes improve code quality, don't just silence errors
Success Criteria
- ✅
npm run checkcompletes with exit code 0 - ✅ No TypeScript errors
- ✅ No ESLint errors or warnings
- ✅ All unused code removed (not just prefixed)
- ✅ Code remains functional after fixes
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.