typescript-code-review-and-linting

Configure ESLint for TypeScript and React code review.

2|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Agentient/vibekit --skill typescript-code-review-and-linting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-code-review-and-linting
Source: https://github.com/Agentient/vibekit/tree/main/plugins/quality-tools/skills/typescript-code-review-and-linting
Command: npx skills add https://github.com/Agentient/vibekit --skill typescript-code-review-and-linting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes TypeScript code quality and React linting practices, helping teams catch type mistakes and anti-patterns early.

Core Features & Use Cases

  • ESLint configuration optimized for TypeScript and React patterns.
  • Enforced rules: no-explicit-any, no-unused-vars, and restricted console usage to improve reliability.
  • Clear code-review guidance to identify type-safety issues and React anti-patterns.
  • Use Case: A project migrating from JavaScript to TypeScript can adopt a consistent linting baseline and review checklist.

Quick Start

Run the configured ESLint workflow on your TS project to surface type-safety and linting issues for rapid remediation.

Frequently Asked Questions about typescript-code-review-and-linting

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

FAQPage Schema
How do I enforce TypeScript type safety and prevent explicit any in my codebase?

TypeScript type safety is enforced by applying an ESLint configuration that uses the no-explicit-any rule to catch type mistakes early. This establishes a consistent linting baseline that prevents unsafe type declarations across your project.

What is the best way to set up React linting rules for a JavaScript to TypeScript migration?

React linting for migrations requires an optimized ESLint configuration that enforces type safety and identifies React anti-patterns. This provides a standardized review checklist to catch type mistakes and ensure consistent code quality during the transition.

Does this ESLint configuration restrict console usage and remove unused variables in TypeScript?

Yes, the ESLint configuration restricts console usage and enforces the no-unused-vars rule. This controlled environment improves overall reliability by preventing debug logging and dead code from persisting in your TypeScript codebase.

How do I identify and fix React anti-patterns during a TypeScript code review?

React anti-patterns are identified using clear code-review guidance that detects type-safety issues and structural mistakes. This process applies React-specific linting rules to flag violations and guide developers toward correct pattern correction.

Can I use this linting workflow without additional dependencies in my existing TS project?

Yes, you can run the configured ESLint workflow directly on your TypeScript project without additional dependencies. It surfaces type-safety and linting issues immediately, allowing for rapid remediation of anti-patterns and rule violations.