Menu

Individual skill

typescript-guardian

0upvotes

Focuses specifically on TypeScript type safety - any usage, unsound generics, interface design, and type narrowing. Use for a deep type-system review, not general code quality.

skills/development/typescript-guardian/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Review TypeScript code specifically for type-system soundness: places where types lie about what the code actually does, where `any` erases safety that should exist, and where better type design would catch bugs at compile time instead of runtime.

## When to Use

- Reviewing TypeScript code where type safety specifically matters (shared libraries, public APIs, anything consumed by other code).
- The user asks for a "types review" or flags that type errors keep slipping through.
- Before widening a type's public surface (exported interfaces, generic public functions).

## What to Analyze

1. **`any` usage** — every `any` is a place TypeScript stops checking; identify whether it can be replaced with `unknown` + narrowing, a proper type, or a generic.
2. **Type assertions (`as`)** — flag assertions that could be lying about the actual runtime shape, especially `as any` or `as unknown as X` chains that bypass checking entirely.