type-fix

Fix TypeScript type errors in files or entire projects.

11|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill type-fix-berkcangumusisik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: type-fix
Source: https://github.com/berkcangumusisik/claude-code-practices/tree/main/skills/type-fix
Command: npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill type-fix-berkcangumusisik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes TypeScript type errors in a file or across the project, reducing debugging toil and aligning code with type safety.

Core Features & Use Cases

  • Detects TypeScript type errors surfaced by the compiler and type-checkers.
  • Groups errors by type, proposes minimal, safe fixes, and applies them with verification.
  • Useful during local development, pre-commit checks, and project migrations to stronger types.

Quick Start

Provide the target file path or omit to fix the whole project.

Frequently Asked Questions about type-fix

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

FAQPage Schema
How do I automatically fix TypeScript type errors across my project?

You can automatically fix TypeScript type errors by running the compiler, grouping errors by type, and applying minimal safe patches to null checks, type mismatches, and improper casts. This process re-checks with tsc --noEmit to ensure zero errors remain.

Can I fix TypeScript type mismatches and improper casts in a single file?

Yes, you can fix TypeScript type mismatches and improper casts in a single file by providing the target file path. The tool reads the code, analyzes tsc outputs, and applies minimal, type-safe fixes directly to that specific file.

What is the best way to resolve missing null checks during a TypeScript migration?

The best way to resolve missing null checks during a TypeScript migration is to use static analysis to detect compiler errors, group them by type, and apply minimal type-safe fixes. This reduces debugging toil and aligns code with stricter type safety requirements.

Do I need to run tsc --noEmit after applying TypeScript type fixes?

Running tsc --noEmit is integrated into the fix process to verify applied changes. After reading code and applying patches to type mismatches and casts, the system re-checks with tsc --noEmit to guarantee zero errors remain in the codebase.

Does this automated TypeScript refactor approach work for pre-commit checks?

Yes, this automated TypeScript refactor approach works for pre-commit checks. It detects type errors surfaced by the compiler, proposes minimal safe fixes, and applies them with verification, making it useful during local development and pre-commit validation.