kieran-typescript-reviewer

Review TypeScript diffs for type safety and maintainability issues.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill kieran-typescript-reviewer-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kieran-typescript-reviewer
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/kieran-typescript-reviewer
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill kieran-typescript-reviewer-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kieran-TypeScript-Reviewer helps ensure robust type safety and clear maintainability during code reviews by prescriptively enforcing a strict set of checks on TypeScript changes.

Core Features & Use Cases

  • Enforce type-safety: flags unsafe any usage, unchecked casts, and nullable flows.
  • Improve readability and maintainability: advocates for explicit types, clearer interfaces, and simpler module boundaries.
  • Regression risk awareness: highlights refactor risks and potential behavior changes when tests are limited.
  • Use Case: applicable when reviewing PRs that modify TypeScript code across modules, utilities, or UI components to prevent erosion of safety and clarity.

Quick Start

Run a strict TypeScript diff review and flag type-safety, readability, and maintainability issues.

Frequently Asked Questions about kieran-typescript-reviewer

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

FAQPage Schema
How do I review TypeScript code for type safety and maintainability issues?

TypeScript code review for type safety involves checking diffs against a strict rubric to flag unsafe any usage, unchecked casts, and nullable flows. This process enforces explicit types and clearer interfaces without executing tests or modifying code.

What does a strict TypeScript code review check for in a pull request?

A strict TypeScript code review checks diffs for type-safety holes, readability issues, and regression risk. It highlights unsafe any usage, unchecked casts, nullable flows, and refactor risks to prevent erosion of safety and clarity across modules.

How do I enforce type safety in TypeScript PRs without running tests?

Type safety in TypeScript PRs can be enforced through static analysis and prescriptive review rubrics. By checking diffs for unsafe casts and nullable flows, you highlight regression risks and maintainability issues without executing tests or modifying code.

Can I use static analysis to flag TypeScript refactor risks in UI components?

Static analysis can flag TypeScript refactor risks in UI components by reviewing diffs for behavior changes and type-safety holes. This approach works across modules and utilities to highlight regression risks when tests are limited.

What is the best way to prevent type safety erosion during TypeScript code reviews?

The best way to prevent type safety erosion during TypeScript reviews is to apply a strict review rubric to diffs. This prescriptively flags unchecked casts and unsafe any usage while advocating for explicit types and simpler module boundaries.