reviewing-typescript

Inspects TypeScript projects and validates code quality, ADR/PDR alignment, and test coverage, outputting APPROVED or REJECTED with findings.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill reviewing-typescript-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-typescript
Source: https://github.com/outcomeeng/claude/tree/main/plugins/typescript/skills/reviewing-typescript
Command: npx skills add https://github.com/outcomeeng/claude --skill reviewing-typescript-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes TypeScript code to identify design flaws and noncompliant patterns that automated gates may miss, ensuring robust architecture and reliable test coverage.

Core Features & Use Cases

  • Deep code comprehension to surface design flaws, risky patterns, and ADR/PDR deviations that affect maintainability and correctness.
  • Evidence-based verification against tests and ADR/PDR constraints to justify approvals or rejections.
  • Comprehensive scope spanning unit-level logic, integration points, and dependency-injection patterns for TypeScript projects.

Quick Start

Inspect a TypeScript project and guide reviewers through a rigorous manual review process.

Frequently Asked Questions about reviewing-typescript

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

FAQPage Schema
How do I perform an adversarial TypeScript code review for strict governance projects?

Adversarial TypeScript code review applies deep comprehension to surface design flaws, verify test coverage, and check ADR/PDR alignment. It evaluates dependency injection and secure coding practices to produce a binary APPROVED or REJECTED verdict with actionable findings.

What is the best way to verify TypeScript code quality against ADR and PDR constraints?

Verifying TypeScript code quality against ADR and PDR constraints requires evidence-based validation of architecture decisions and test coverage. The process ensures explicit dependency injection compliance and secure coding practices to yield a binary approval or rejection decision.

Can I use deep code comprehension to find noncompliant TypeScript patterns that automated gates miss?

Deep code comprehension identifies noncompliant TypeScript patterns, risky design flaws, and ADR/PDR deviations that automated gates miss. It analyzes integration points and dependency injection patterns to justify approvals or rejections with actionable evidence.

Does TypeScript code review provide actionable findings when a project is rejected?

TypeScript code review provides actionable findings when a project is rejected, detailing specific design flaws, test coverage gaps, and ADR/PDR deviations. When approved, it returns a binary verdict with no notes required.

When do I need manual TypeScript code review instead of automated security and testing gates?

Manual TypeScript code review is needed for strict governance requirements where automated gates miss deep design flaws, noncompliant patterns, and ADR/PDR misalignment. It validates test coverage and secure coding practices through rigorous evidence-based inspection.