reviewing-typescript-tests

Enforce spec-compliant TypeScript unit, integration and e2e test reviews with property-based testing checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps ensure TypeScript tests provide evidentiary value and meet spec compliance by extending foundational review workflows with TS-specific testing patterns, property-based testing requirements, and code-quality checks.

Core Features & Use Cases

  • TS-specific extension to /reviewing-tests, adding Phase 5 patterns for property-based testing, property coverage checks, and TypeScript code quality guidance
  • Test structure guidance for file naming conventions and linkage (e.g., .unit.test.ts, .integration.test.ts, .e2e.test.ts) to improve traceability
  • Quality gates enforcing absence of mocks, explicit return types in helpers, and meaningful properties in property tests
  • Use Case: When reviewing a TS project, apply these rules to ensure unit, integration, and end-to-end tests align with spec-driven goals

Quick Start

Activate this skill before reviewing TypeScript tests to enforce TS-specific review rules and property-based testing requirements.

Frequently Asked Questions about reviewing-typescript-tests

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

FAQPage Schema
How do I review TypeScript tests for evidentiary value and spec compliance?

To review TypeScript tests for evidentiary value, apply spec-driven rules that enforce property-based testing patterns, check property coverage, and validate code quality during code reviews.

What is property-based testing in TypeScript code reviews?

Property-based testing in TypeScript code reviews involves enforcing meaningful properties in test cases, checking property coverage, and ensuring tests meet spec-driven goals without relying on mocks.

How do I enforce TypeScript test file naming conventions for traceability?

Enforce TypeScript test file naming conventions by requiring specific suffixes like .unit.test.ts, .integration.test.ts, and .e2e.test.ts to improve test structure linkage and spec traceability.

Do I need explicit return types in TypeScript test helper functions?

Yes, TypeScript test reviews require explicit return types in helper functions as a quality gate to ensure code quality and maintain spec compliance across unit, integration, and end-to-end tests.

What are the limitations when reviewing TypeScript tests with property-based testing?

Limitations include strict quality gates that enforce the absence of mocks and require meaningful properties in property tests, which may require rewriting existing test suites to achieve spec compliance.