multiAI Summary Pending
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.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/lint-typecheck/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/applelamps/lint-typecheck/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lint-typecheck/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lint-typecheck Compares
| Feature / Agent | lint-typecheck | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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