code-review

legacy3's avatarfrom legacy3

Review code for Effect-TS patterns, common issues, and project conventions. Use when reviewing PRs, checking code quality, or before committing changes.

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026
[Code Review]

When & Why to Use This Skill

This Claude skill provides an automated, high-precision code review mechanism specifically tailored for Effect-TS ecosystems and modern TypeScript projects. It enforces architectural consistency by validating Effect-TS patterns, branded type implementations, and React component conventions, ensuring code quality and type safety across the development lifecycle.

Use Cases

  • Pull Request Automation: Streamline the PR review process by automatically checking for Effect-TS anti-patterns, such as improper async/await usage instead of yield*.
  • Pre-commit Quality Checks: Validate local code changes against project-specific conventions like Branded IDs and Jotai atom placement before pushing to the repository.
  • Technical Debt Reduction: Identify and refactor legacy code patterns, such as unsafe type casts or missing 'satisfies' operators, to improve overall codebase maintainability.
  • Frontend Architecture Enforcement: Ensure Next.js and React portal components adhere to strict loading state patterns, barrel export rules, and proper 'use client' directive usage.
  • Standardizing Error Handling: Automatically verify that services and layers use Data.TaggedError and proper Context.Tag patterns for robust dependency injection.
namecode-review
descriptionReview code for Effect-TS patterns, common issues, and project conventions. Use when reviewing PRs, checking code quality, or before committing changes.
allowed-toolsRead, Grep, Glob

Code Review

Read-only review skill for checking code quality against project conventions.

Checklist

Effect-TS Patterns

  • Uses Effect.gen with yield*, not async/await
  • No type casts (as Type) - use satisfies instead
  • Errors are Data.TaggedError with descriptive payloads
  • Services use Context.Tag or Effect.Service pattern
  • Layers properly compose dependencies

Branded IDs (wowlab-core)

  • Schema + Brand dual pattern for IDs
  • eslint-disable no-redeclare comment present
  • Validation logic matches between Schema and Brand

Portal Components

  • Pages are minimal (just render component)
  • loading.tsx uses *Skeleton component
  • "use client" only where needed
  • Barrel exports in index.ts
  • Jotai atoms in domain folders under atoms/
  • Uses @/lib/format utilities (not raw .toLocaleString() or manual formatting)
  • Loading states use Flask components (not Loader2 from lucide)
  • Providers export hook + Provider + types from providers/index.ts

General

  • No unused imports or variables
  • No console.log in production code
  • Error handling is comprehensive
  • Types are explicit at module boundaries
  • Control flow has braces (no single-line if/for)
  • No backwards-compat shims or deprecated code

How to Use

  1. I'll read the files you want reviewed
  2. Check against the patterns above
  3. Report issues with file:line references
  4. Suggest fixes where applicable

Common Issues

Wrong

const data = await fetchData(); // async/await
const x = foo as Bar; // type cast

const data = yield * fetchData(); // Effect.gen
const x = foo satisfies Bar; // satisfies