typescript-check

# TypeScript Type Check Skill ## Overview This skill validates TypeScript code by running `tsc --noEmit` and parsing errors into structured, actionable reports organized by file. It is a **read-only validation** step (does not modify code) that implements a linear workflow: locate config → execute compiler → parse output → present results. Use this skill when validating TypeScript code before commits, after refactors, or checking for type regressions. Do not use for linting, test execution, runtime errors, or projects without tsconfig.json. --- ## Instructions ### Step 1: Verify TypeScript Project Locate tsconfig.json in the project. This step is mandatory—never skip it. tsc without a tsconfig.json falls back to default settings, missing project-specific configuration like paths, strict mode, and compiler targets. ```bash ls tsconfig.json 2>/dev/null || ls */tsconfig.json 2>/dev/null ``` If no tsconfig.json exists, stop and inform the user. Do not proceed without configuration. **Why**: Running without tsconfig.json produces unreliable results that don't match the project's actual settings. ### Step 2: Run Type Check Execute the TypeScript compiler in type-check-only mode using `--noEmit`: ```bash npx tsc --noEmit 2>&1 ``` Capture the exit code: - **Exit 0**: No type errors found. Report PASS. - **Exit 1+**: Type errors detected. Continue to Step 3. Do not install TypeScript or dependencies. If TypeScript is not installed, inform the user and suggest `npm insta...