review-patterns

Review TypeScript code changes for Effect-TS pattern compliance.

21|4|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill review-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-patterns
Source: https://github.com/tylerjrbuell/reactive-agents-ts/tree/main/.agents/skills/review-patterns
Command: npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill review-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a systematic checklist to identify Effect-TS style and architecture violations in code changes, enabling consistent, project-wide code reviews and faster PR approvals.

Core Features & Use Cases

  • Comprehensive Checklist: Nine focused categories covering types, errors, services, state, async handling, layer composition, imports/exports, LLM service usage, and kernel extensions.
  • Precise Findings: Instructs reviewers to report PASS/FAIL per category, list offending files and line locations, and provide suggested fixes.
  • Use Case: Run this Skill when reviewing pull requests, finalizing package submissions, or auditing modified files to ensure they conform to Reactive Agents' Effect-TS conventions.

Quick Start

Run the review-patterns skill on the target file-or-package-path to produce a PASS/FAIL checklist with specific file and line references.

Frequently Asked Questions about review-patterns

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

FAQPage Schema
How do I review Effect-TS patterns in a pull request?

Review Effect-TS patterns by statically inspecting TypeScript source files to verify Schema-based types, Data.TaggedError usage, Effect.Effect returns, Ref-based state, Layer factories, and .js relative imports, producing a PASS/FAIL checklist with file and line references.

What is Effect-TS pattern compliance for TypeScript repositories?

Effect-TS pattern compliance ensures TypeScript code uses Schema-based types, Data.TaggedError for errors, Effect.Effect returns for async operations, Ref for state, and Layer factories for composition, validated through static source file inspection.

How do I audit TypeScript files for Effect-TS layer composition and error handling?

Audit TypeScript files by statically checking for Layer factory usage in layer composition and Data.TaggedError in error handling, reporting PASS or FAIL with specific offending file names and line locations.

Can I use static analysis to validate Effect-TS service and state patterns in a monorepo?

Yes, static analysis validates Effect-TS service and state patterns by inspecting TypeScript source files for service definitions and Ref-based state management, reporting explicit PASS/FAIL results with file and line citations across monorepo packages.

What's the best way to check .js relative imports in Effect-TS code changes?

Check .js relative imports by running static inspection on TypeScript source files to verify import paths conform to Effect-TS conventions, generating a PASS/FAIL report with specific file and line citations for any violations.

Why does my Effect-TS code review fail on Data.TaggedError usage?

Effect-TS code review fails on Data.TaggedError usage when static inspection of TypeScript source files identifies non-compliant error handling patterns, reporting the offending files and line locations with suggested fixes.