typecheck

Runs TypeScript type checking and fixes all reported type errors.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill typecheck-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typecheck
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/typecheck
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill typecheck-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Type errors often slip into TypeScript codebases during rapid development, blocking commits and breaking builds. This Skill runs the project's type checker, interprets every diagnostic, and fixes errors one at a time without resorting to unsafe shortcuts like any or @ts-ignore. ## Core Features & Use Cases - Automated Type Checking: Runs npm run typecheck or npx tsc --noEmit and interprets each diagnostic. - Safe Error Resolution: Fixes type mismatches with proper annotations, never using any or @ts-ignore as shortcuts. - Iterative Verification: Re-runs the type checker until it exits with code 0 and zero diagnostics. - Use Case: Before committing changes to a TypeScript monorepo, invoke this Skill to discover all type errors, fix them with minimal correct changes, and confirm a clean typecheck pass. ## Quick Start Run the typecheck skill to find and fix all TypeScript type errors in this project before I commit.

Frequently Asked Questions about typecheck

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

FAQPage Schema
How do I check TypeScript types without emitting files?▼

Run npx tsc --noEmit to type check a TypeScript project without generating output files. Many projects also expose this as an npm script such as npm run typecheck, which exits with code 0 when no diagnostics remain.

How to fix TypeScript type errors without using any?▼

Fix type errors by adding proper type annotations and correcting type mismatches at their source. Avoid shortcuts like any, as casts, or @ts-ignore, since they suppress diagnostics without resolving the underlying type safety issue.

Why does tsc --noEmit still report errors after fixes?▼

Fixing one error can reveal new diagnostics in dependent code paths, so a single pass rarely clears everything. Re-run the type checker after each fix until it exits with code 0 and reports zero diagnostics.

When should I run TypeScript type checking in my workflow?▼

Run type checking before every commit to catch type errors early and keep the build green. It is also useful after refactoring, dependency upgrades, or merging branches that touch shared type definitions.

What counts as an unsafe fix for TypeScript errors?▼

Unsafe fixes include using the any type, adding @ts-ignore comments, or forcing casts with as to silence the compiler. These hide real type mismatches and undermine the strict mode guarantees the project relies on.