typescript-check

Run tsc --noEmit and generate file-grouped TypeScript error reports.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill typescript-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-check
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/typescript-check
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill typescript-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run TypeScript type checking with tsc --noEmit and parse errors into actionable, file-grouped output. Use when validating TypeScript code before commits, after refactors, or when checking for type regressions. Use for "type check", "tsc", "TypeScript errors", "type validation", or pre-commit TypeScript verification. Do NOT use for linting, test execution, runtime errors, or JavaScript-only projects without tsconfig.json.

Core Features & Use Cases

  • Provides structured error reports with file, line, and error code, helping you quickly locate issues.
  • Groups errors by file and shows absolute paths to simplify navigation in large codebases.
  • Supports pre-commit checks and CI workflows by reliably reporting PASS/FAIL status.

Quick Start

Run tsc --noEmit across your TS project to generate a structured error report without emitting JavaScript.

Frequently Asked Questions about typescript-check

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

FAQPage Schema
How do I run a TypeScript type check and group errors by file?

Validate your TypeScript project by running tsc --noEmit to generate a structured, file-grouped error report. It identifies the tsconfig, executes the compiler, and reports PASS or FAIL with specific error details grouped by absolute file paths.

Does tsc --noEmit work for monorepos with multiple tsconfig files?

Yes, project validation supports monorepos with multiple tsconfig files. It identifies each tsconfig, executes the TypeScript compiler, and produces structured, file-grouped error reports detailing PASS or FAIL status for each configuration.

Why does TypeScript validation fail to parse errors without a tsconfig.json?

TypeScript validation requires a tsconfig.json to identify project configuration and execute the compiler. It cannot parse structured, file-grouped error reports for JavaScript-only projects lacking this configuration file.

What is the best way to check for TypeScript type regressions before a commit?

Run tsc --noEmit to generate a structured, file-grouped error report for checking TypeScript type regressions before a commit. This reliably reports PASS or FAIL status, making it suitable for pre-commit checks and CI workflows.

Can I use tsc --noEmit output for linting or test execution?

No, tsc --noEmit output is strictly for TypeScript type validation and error reporting, not linting or test execution. It parses compiler errors into structured, file-grouped reports to help locate issues during refactors or regression checks.