tsc-trace-analyzer

tsc-trace-analyzer

Run tsc --generateTrace on a TypeScript project, parse the resulting trace files, identify compilation bottlenecks, and suggest concrete code fixes.

When to use

Use this skill whenever the user complains that the TypeScript compiler or compilation is slow, or when they want to investigate where tsc is spending time. Triggers include — but are not limited to — any of the following:

• "The TypeScript compiler is slow" / "tsc is slow" / "compilation is slow"
• "My TypeScript build is slow" / "the build takes forever"
• "Type checking is slow" / "type checking takes forever" / "tsc takes forever"
• "Why is my TypeScript project so slow to compile?"
• "How do I make tsc faster?" / "How do I speed up TypeScript?"
• "Find TypeScript performance bottlenecks" / "Find type-checking hotspots"
• "Profile the TypeScript compiler" / "profile tsc"
• Any mention of --generateTrace, trace.json, types.json, "tsc trace", or "TypeScript tracing"
• tsc is crashing with a JavaScript heap out-of-memory error and the user wants to understand or fix it
• The user wants to know what the TypeScript compiler is spending its time on
• The user asks for help reducing TypeScript compile times, build times, or CI times caused by tsc

Also use it proactively if the user shares a slow tsc build log, a long type-checking duration, or asks for advice on TypeScript performance optimization.

Instructions

Follow these steps in order:

Step 1: Find tsconfig.json

Search for tsconfig.json files in the project:

• Use Glob to find **/tsconfig.json files, excluding node_modules
• If exactly one is found, use it
• If multiple are found, pick by this priority order:
  1. Root tsconfig.json at the project root — use it if present
  2. src/tsconfig.json — use it if there is no root tsconfig
  3. Otherwise, ask the user which one to analyze
• If none are found, tell the user this skill requires a TypeScript project with a tsconfig.json