verify-ts

Audits TypeScript code for type-safety, strictness, and idiomatic patterns against a defined rule set.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill verify-ts-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-ts
Source: https://github.com/andrewcodesit/skills/tree/main/skills/engineering/verify-ts
Command: npx skills add https://github.com/andrewcodesit/skills --skill verify-ts-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? TypeScript code often compiles green while hiding type-safety holes like unjustified any, unsafe as casts, non-null assertions, and loose tsconfig settings. This Skill performs a rigorous audit that treats types as proof of behavior, catching real risks instead of rubber-stamping a passing build. ## Core Features & Use Cases - Rule-Based Type Audit: Applies 16 defined rules covering no-any policy, unknown narrowing at boundaries, discriminated unions, exhaustiveness checks, branded types, and readonly data. - tsconfig Strictness Check: Verifies strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, and related flags, flagging missing ones as blockers. - Classified Findings Report: Outputs findings as Blocker, Strict, Improve, or Style with file:line citations and concrete fixes, saved to a persistent audit report path. - Use Case: Before merging a feature branch, run the audit on the diff against main to catch type-safety regressions and receive a saved report with a PASS / NEEDS WORK / BLOCKED verdict. ## Quick Start Ask the agent to run a TypeScript audit on the current branch diff or on specific files you name.

Frequently Asked Questions about verify-ts

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

FAQPage Schema
How do I audit TypeScript code for type safety?▼

Run the audit on a branch diff or named files. It reads each full file plus the tsconfig, applies 16 type-safety rules, and returns findings classified as Blocker, Strict, Improve, or Style with file:line references and concrete fixes.

What TypeScript strictness rules does the audit check?▼

It checks 16 rules including no unjustified any, unknown at boundaries, avoiding unsafe as casts, eliminating non-null assertions, discriminated unions for state, exhaustiveness checks, branded primitives, readonly data, and type-only imports.

Does the audit check tsconfig strict settings?▼

Yes. It reads tsconfig.json and flags missing strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, noImplicitAny, and strictNullChecks. A missing strict flag is treated as a blocker since loose config invalidates the audit.

Can I audit only specific files instead of the whole branch?▼

Yes. If you name files or a diff, the audit scopes to those. Without a scope, it defaults to diffing the current branch against main across .ts, .tsx, and .vue files.

Where is the TypeScript audit report saved?▼

The full report is written to ~/.agents/ts-audits/<repo>/<slug>-ts-audit.md. Only the saved path is printed to the terminal, not the full report body.