code-reviewer-typescriptlisted

## Positioning Focused on **TypeScript language-level** type system and code structure review. Checks whether types are rigorous, designs are sound, and modules are clear. Difference from `code-reviewer-react`: React skill focuses on component design and Hooks; this skill focuses on TS type gymnastics and module design. Difference from `code-reviewer-nodejs`: Node.js skill focuses on runtime behavior; this skill focuses on compile-time type safety. **Execution timing**: When reviewing `.ts` files (non-React components) **Scan scope**: Specified files, or file list obtained via `git diff` --- ## Review Process ### Step 1: Determine Review Scope Determine files to review by priority: 1. Files or directories explicitly specified by user 2. User mentions PR or branch → run `git diff --name-only <base>..HEAD` to get changed files 3. User says "look at recent changes" → run `git diff --name-only HEAD~1` 4. None of the above → ask user which files to review Only review `.ts` files. Skip test files (`*.test.*` / `*.spec.*`), type declaration files (`*.d.ts`), and config files. For `.tsx` files, use the `code-reviewer-react` skill instead. ### Step 2: Per-file Review Read the complete file content first, understand context, then check each item. Execute the following review items for each file. ### Step 3: Summary Report Generate a structured report using the output template at the bottom. --- ## Review Checklist ### 1. Type Safety The type system is TypeScript's core