tsc-error-triage

Diagnose TypeScript compiler errors and group them by root cause.

1|1|Updated May 3, 2026

Search Tags:#typescript #workspace #refactor #triage #root-cause #tsc #typecheck

Ready to run

npx skills add https://github.com/matt-riley/agent-skills --skill tsc-error-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tsc-error-triage
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/tsc-error-triage
Command: npx skills add https://github.com/matt-riley/agent-skills --skill tsc-error-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnosing and triaging TypeScript compiler errors efficiently by prioritizing root-cause fixes rather than patching multiple leaf errors.

Core Features & Use Cases

Root-cause-first triage that maps errors to their origin.
Grouping errors by root symbol, module, or config boundary to guide repairs.
Use Case: after a refactor or dependency upgrade, quickly stabilize the codebase by fixing the root surface.

Quick Start

Run the repository typecheck, capture the full error output, and identify the first root-cause before patching downstream errors.

Frequently Asked Questions about tsc-error-triage

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

FAQPage Schema

How do I triage TypeScript compiler errors after a dependency upgrade?▼

Group TypeScript compiler errors by root symbol, module, or config boundary to identify the origin. This root-cause-first triage approach maps errors to their source, guiding repairs and stabilizing the codebase efficiently after refactors or dependency upgrades.

How do I group TypeScript errors by root cause across multiple packages?▼

Why am I getting a burst of TypeScript errors after changing my tsconfig?▼

Run the repository typecheck command to capture the full error output, identify the first root cause, and fix the origin surface. After patching the root issue, re-run the typecheck to verify that downstream errors are resolved.

What is the best way to fix multiple TypeScript errors without patching each one individually?▼

The best way to fix multiple TypeScript errors is to map errors to their root cause and fix the origin surface first. By grouping errors by root symbol or module, you resolve many leaf errors with a single targeted repair.

Does root-cause TypeScript triage work for errors across different packages in a workspace?▼

Yes, root-cause TypeScript triage applies when a repo produces errors across one or more packages. It groups errors by config boundary or root symbol to guide repairs and stabilize the entire workspace after refactors.