kieran-typescript-reviewer

Review TypeScript code diffs for type safety and regression risks.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill kieran-typescript-reviewer-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kieran-typescript-reviewer
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/agent-kieran-typescript-reviewer
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill kieran-typescript-reviewer-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript code reviews often miss critical type safety holes, hidden regression risks, and maintainability issues that lead to runtime errors, technical debt, and hard-to-debug production incidents, especially in legacy codebases or after large refactors.

Core Features & Use Cases

  • Type Safety Gap Detection: Flags unsafe type casts, unchecked nullable flows, any usage, and type assertions that disable the TypeScript type checker, preventing runtime type errors.
  • Structural Regression Identification: Catches changes that make existing modules harder to reason about, such as mixed-concern service files, hook-heavy components, or utility modules with accumulated unrelated logic.
  • Regression Risk Assessment: Highlights behavior that was moved or removed during refactors with no evidence that call sites, consumers, or tests still cover the changed functionality.
  • Use Case: For example, when a team refactors a legacy user authentication service, this skill catches an unsafe as User cast that would bypass type checking and flags that the service now handles both authentication and user notification logic, prompting a split into separate, testable modules.

Quick Start

Use the kieran-typescript-reviewer skill to review the latest TypeScript code diff for type safety issues, structural regressions, and testing gaps.

Frequently Asked Questions about kieran-typescript-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect type safety holes during a TypeScript code review?

TypeScript code reviews identify type safety holes by flagging unsafe type casts, unchecked nullable flows, any usage, and type assertions that disable the TypeScript type checker. This prevents runtime type errors and reduces technical debt.

What is structural regression identification in TypeScript refactoring?

Structural regression identification catches changes that make TypeScript modules harder to reason about, such as mixed-concern service files, hook-heavy components, or utility modules with accumulated unrelated logic. It maintains codebase maintainability during refactors.

How do I assess regression risks when refactoring legacy TypeScript code?

Assess TypeScript regression risks by highlighting behavior that was moved or removed during refactors with no evidence that call sites, consumers, or tests still cover the changed functionality. This surfaces hidden testing gaps in legacy codebases.

Can I use static analysis to find difficult-to-test logic in UI components and service files?

Yes, static analysis can surface logic that is difficult to test across service files, UI components, and utility modules. By enforcing strict type safety standards, it flags mixed-concern files and hidden testing gaps to reduce runtime errors.

When do I need rigorous type safety enforcement for pull request reviews?

You need rigorous type safety enforcement for pull request reviews when validating refactors or maintaining legacy TypeScript code. It flags unsafe type assertions and regression risks from removed behavior, preventing hard-to-debug production incidents.