ts-typecheck-triage

Triages TypeScript compiler errors and applies minimal fixes in validated waves.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/arslan9024/White-Caves --skill ts-typecheck-triage-arslan9024
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ts-typecheck-triage
Source: https://github.com/arslan9024/White-Caves/tree/main/.github/skills/ts-typecheck-triage
Command: npx skills add https://github.com/arslan9024/White-Caves --skill ts-typecheck-triage-arslan9024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? TypeScript projects often accumulate large batches of compiler errors that block implementation progress, and fixing them one by one without a strategy wastes time and introduces regressions. This Skill provides a structured workflow to group errors by root cause, fix the highest-leverage issues first, and verify each change with focused and broad validation runs. ## Core Features & Use Cases - Root-Cause Grouping: Clusters diagnostics from tsc --noEmit by category such as imports, typings, model mismatches, and syntax errors. - Minimal Safe Fixes: Prefers API/name alignment and local fallbacks over aliases, keeping edits small and reversible. - Verified Reporting: Re-runs focused then broader validation and reports error counts before and after, plus remaining blockers by file and category. - Use Case: When a refactor breaks the build with dozens of tsc errors across a Redux Toolkit codebase, use this Skill to triage the errors, fix the root causes in waves, and confirm the error count drops to zero. ## Quick Start Triage the current TypeScript errors in this project, fix the highest-leverage root causes first, and report the error count before and after.

Frequently Asked Questions about ts-typecheck-triage

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

FAQPage Schema
How do I fix a large number of TypeScript errors efficiently?▼

Group the errors by root cause such as imports, typings, model mismatches, or syntax, then fix the highest-leverage cause first. Re-run focused validation after each fix and broader validation afterward to confirm the error count actually drops.

How to triage tsc --noEmit errors in a project?▼

Capture the full diagnostic set with tsc --noEmit, cluster errors by category, and address root causes rather than individual symptoms. Prefer aligning API or name mismatches over adding aliases, and keep every edit minimal and reversible.

What should I do when store exports are missing in TypeScript?▼

Prefer a local state or service fallback instead of forcing an import that does not exist. This keeps the fix contained and avoids cascading changes across modules that depend on the missing export.

Why does terminal output not match actual TypeScript error counts?▼

Terminal output can lag or buffer, so corroborate it with editor diagnostics or a fresh compiler run. Always update trackers only with verified numbers from a completed validation pass.

When should I not use a triage workflow for type errors?▼

Avoid wave-based triage when errors stem from a single known breaking change that can be reverted directly. Triage adds the most value when errors span multiple files and root causes are unclear.