How does the Review Type Safety skill improve my code?

It acts as a specialized auditor that catches subtle TypeScript issues that standard linters might miss, such as logic holes in type narrowing or lazy 'any' usage.

Does this skill require a specific TypeScript version?

The skill analyzes standard TypeScript patterns and best practices, making it compatible with most modern TypeScript configurations and versions.

Is this skill useful for large-scale refactoring?

Absolutely. It is particularly effective during refactoring to ensure that moving code or changing interfaces hasn't created 'unknown' type leaks or unhandled states.

Can I use this skill to review specific files?

Yes, you can pass specific file paths or arguments to the skill, or let it automatically analyze the git diff between your current branch and main.

Review Type Safety

Name: Review Type Safety
Author: doodledood

bydoodledood

•

Security & Testing

Audits TypeScript code for type safety violations, including any/unknown abuse, unhandled states, and missing type narrowing.

About

The Review Type Safety skill provides an automated audit layer for TypeScript projects, helping developers maintain high-integrity codebases. It identifies common anti-patterns such as the overuse of the 'any' type, detects logically unreachable or invalid states, and flags instances where type narrowing is missing or incomplete. By leveraging Git integration, the skill can automatically analyze differences between branches, making it an essential tool for ensuring that new PRs don't introduce type regressions or hidden technical debt.

Key Features

Identifies 'any' and 'unknown' type abuse in TypeScript code
Analyzes Git diffs between branches for targeted reviews
8 GitHub stars
Detects missing type narrowing and unhandled union cases
Provides actionable recommendations for improving type definitions
Flags logically invalid or impossible code states

Use Cases

Auditing legacy TypeScript files for strict type compliance
Automating type-safety checks during the code review process
Comparing feature branches against main to prevent type regressions

About

Key Features

Identifies 'any' and 'unknown' type abuse in TypeScript code
Analyzes Git diffs between branches for targeted reviews
8 GitHub stars
Detects missing type narrowing and unhandled union cases
Provides actionable recommendations for improving type definitions
Flags logically invalid or impossible code states

Use Cases

Auditing legacy TypeScript files for strict type compliance
Automating type-safety checks during the code review process
Comparing feature branches against main to prevent type regressions