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.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill lint-typecheckAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.0 KB, 199 tokens by cl100k_base, as published. Nobody here has run it
Lint and Type Check
Instructions
-
Navigate to frontend directory and run lint:
cd frontend && npm run lint -
Run TypeScript compilation check (no emit):
cd frontend && npx tsc -b --noEmit -
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
-
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
--fixwith user confirmation - Do not modify tsconfig.json to suppress errors
- Report all issues before attempting fixes
What ships with it: 1 file
11.4 KB alongside SKILL.md
- skill-report.json11.4 KB