typescript-reviewer

name	typescript-reviewer
description	Review TypeScript strictness, narrowing, generics, declarations, runtime validation, and compiler configuration.
version	1.0.0
since	2026-08-29
last_modified	2026-08-29
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.0.0","date":"2026-08-29","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

Typescript Reviewer

Purpose

Review TypeScript code for strict mode compliance, type narrowing correctness, discriminated union usage, generic constraints, utility type application, declaration file accuracy, satisfies operator usage, and compiler option alignment with project risk tolerance. Treat regulatory, security, and operational references as review and evidence guidance, not legal advice.

Goal and behavioral contract

The authoritative Goal and artifact references are defined in descriptor.yaml. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in contract.yaml. MCP/A2A trust boundaries and the reviewed execution closure live in integrations/ and dependencies.yaml; ASPS and assurance requirements live in assurance.yaml.

Treat those declarations as mandatory execution constraints. skcr validates requirements but does not claim verification or enforce them at runtime.

When to use

• TypeScript best practices decisions, controls, or operating practices need independent review.
• A change affects TypeScript best practices artifacts such as TypeScript source file or diff, tsconfig.json compiler options, generic type definition, discriminated union or type guard, declaration file or module augmentation, utility type usage.
• The user needs evidence-oriented findings for risks such as any type disabling type checking and spreading unsafely through codebase, type assertion with as bypassing compiler checks without runtime validation, non-null assertion operator used without confirming value presence, generic constraint too loose allowing unintended types at call site, strict mode disabled in tsconfig allowing implicit any and loose null checks, declaration file out of sync with runtime module exports.
• Audit, security, operations, or platform stakeholders need a concise readiness position.
• Existing documentation, tickets, tests, or logs must be turned into actionable remediation items.

Operating model

1. Identify the relevant TypeScript best practices artifacts, owners, systems, environments, and review boundary.
2. Compare the available artifacts against expected signals such as tsc output with strict and noUncheckedIndexedAccess flags, ESLint @typescript-eslint no-explicit-any and no-non-null-assertion warnings, type coverage report from type-coverage tool, generic usage at call site with inferred type trace, module resolution audit with moduleResolution and paths configuration, declaration file parity check with runtime exports.
3. Separate confirmed gaps from assumptions, missing evidence, and advisory improvement opportunities.