← ClaudeAtlas

ts-auditlisted

Audit TypeScript and React code against expert-level best practices from 9 Total TypeScript library references. Use when the user wants to review, audit, check, or improve TypeScript code quality — including requests like "audit this file", "review my types", "check my TypeScript", "what's wrong with this code", "improve my TS", "type review", or any request to evaluate TypeScript code against modern patterns. Also use when the user mentions type safety, generics review, or React TypeScript patterns. Covers type safety, generics, narrowing, branded types, discriminated unions, React TypeScript patterns, type transformations, testing patterns, and mocking techniques.
chrislacey89/skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill chrislacey89/skills
# TypeScript Audit Audit TypeScript code against 9 expert-level references covering type safety, generics, advanced patterns, React integration, type transformations, and testing. The goal is to surface concrete improvements the author may not have considered — not to nitpick style, but to catch real type-safety gaps, missed narrowing opportunities, and patterns that would make the code more robust. ## Invocation The user provides a target: a file path, directory, or glob pattern. Examples: - `/ts-audit src/db/queries.ts` - `/ts-audit src/pipeline/` - `/ts-audit src/**/*.tsx` ## Invocation Position This is a side-route skill for TypeScript code quality auditing, not a default pipeline step. Use `/ts-audit` when you want to audit TypeScript or React code against expert-level patterns from the Total TypeScript library references — whether on a single file, a directory, or a glob of changed files. Do not use it as a substitute for `/pre-merge` architectural review (which checks structural principles) or `/tdd` (which enforces red-green-refactor). It complements both by focusing specifically on type-safety gaps and TypeScript idiom improvements. For TypeScript projects, `/ts-audit` pairs naturally with `/pre-merge` Phase 3 (Architectural Review) — running it on changed files provides type-safety analysis that complements the seven structural dimensions. ## Step 1: Read the target code - **Single file**: read it directly - **Directory**: glob for `**/*.ts` and `**/*.tsx