Accelerate required type checking with a native compiler

Linear switched its type check to tsgo, the native TypeScript compiler.

Prompt

Evaluate and apply this CI technique to my repository: Accelerate required type checking with a native compiler.

Linear switched its type check to tsgo, the native TypeScript compiler.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/native-type-checking.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Linear used this technique

Read what Linear changed and follow the original sources.

Accelerate required type checking with a native compiler

Linear switched its type check to tsgo, the native TypeScript compiler, and the weekly median of the tsc check fell 73%. The published prompt translates that change into the catalog’s TypeScript 7 compatibility checks.

Use it when: A qualifying no-emit type check is the long-running step on the merge path.
Before applying it: Compiler API consumers and changed defaults need a compatibility plan. Keep both checks until outputs match; emitting builds do not qualify for this recipe.

How Linear used this technique

Accelerate required type checking with a native compiler

Related techniques

Use a faster native linter without losing rules

Company Playbooks