typescript-eslint

Diagnose TypeScript compilation errors and ESLint violations in projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/B16B1RD/cc-craft-kit --skill typescript-eslint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-eslint
Source: https://github.com/B16B1RD/cc-craft-kit/tree/main/.claude/skills/typescript-eslint
Command: npx skills add https://github.com/B16B1RD/cc-craft-kit --skill typescript-eslint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, eslint.

What problem does it solve?

Maintaining high code quality in TypeScript projects can be challenging, with type errors and style violations often slipping through. This skill automates the detection of compilation errors and ESLint violations, ensuring your codebase remains robust, consistent, and error-free.

Core Features & Use Cases

  • TypeScript Compilation Analysis: Automatically detect type errors, missing definitions, and strict mode compliance issues.
  • ESLint Rule Enforcement: Enforce code style, naming conventions, and identify potential bugs like unused variables or code smells.
  • Code Quality Metrics: Provides insights into cyclomatic complexity, code duplication, and unused code.
  • Use Case: Before submitting a code review, run this skill on your feature branch. It will automatically highlight all TypeScript compilation errors and ESLint warnings, allowing you to fix them proactively and submit clean, high-quality code.

Quick Start

Analyze the TypeScript code in the 'src/' directory for any compilation errors or ESLint violations, and suggest fixes.

Frequently Asked Questions about typescript-eslint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch TypeScript type errors and ESLint violations before code review?

Run TypeScript compilation analysis and ESLint rule enforcement on your codebase to automatically detect type errors, style violations, unused variables, and code quality issues. This identifies problems early so you can fix them proactively before submitting changes.

Can I enforce TypeScript strict mode compliance and naming conventions in my project?

Yes. TypeScript compilation analysis detects strict mode compliance issues while ESLint rule enforcement checks naming conventions, code style, and potential bugs. Configure tsconfig.json and .eslintrc to define your project's standards.

What types of code quality issues does ESLint detect in TypeScript projects?

ESLint identifies unused variables and imports, code smells, naming convention violations, and style inconsistencies. Combined with TypeScript analysis, it provides cyclomatic complexity metrics and code duplication insights for comprehensive quality assessment.

How do I automate code quality checks in my CI pipeline?

Integrate TypeScript compilation and ESLint rule enforcement into your CI workflow to run automatically on pull requests and commits. This ensures all code meets type safety and style standards before merging.

Do I need both TypeScript and ESLint configured to use this skill?

Yes. The skill requires both typescript and eslint as dependencies. You'll need tsconfig.json for TypeScript compilation settings and .eslintrc for linting rules to run comprehensive analysis on your source code.

Can this skill auto-fix ESLint violations or only report them?

The skill enforces ESLint rules and provides actionable remediation guidance. Many ESLint violations support auto-fix; you can apply fixes through standard lint commands to resolve issues automatically.