effect-review

Analyze code changes for Effect-TS compliance and generate remediation reports.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill effect-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-review
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/effect-review
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill effect-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, multi-agent review workflow to evaluate code changes against Effect-TS conventions, branded types, observability, error handling, test coverage, and UI quality.

Core Features & Use Cases

  • Orchestrates a multi-agent assessment by discovering changed files, categorizing them, and launching specialized reviewers in parallel.
  • Produces a unified Effect Review Report highlighting Critical/Warning/Info findings across primitives, branded types, OTEL, error handling, tests, and UI quality.
  • Supplies an actionable remediation plan and scoring to guide improvements across the codebase.

Quick Start

Run the effect-review workflow on your current changes to generate a standardized, multi-facet report.

Frequently Asked Questions about effect-review

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

FAQPage Schema
How do I review Effect-TS code changes for branded types and observability compliance?

To review Effect-TS code changes, you analyze PR diffs or staged changes to verify compliance with branded types, observability, error handling, and test coverage. The process categorizes files into backend, tests, and UI to produce a unified, actionable remediation report.

What is the best way to enforce Result.builder patterns and prevent raw fetch usage in Effect-TS?

The best way to enforce Result.builder patterns is through an automated Effect-TS code review. It flags raw fetch usage against internal backends and missing Result.builder patterns, generating a structured remediation plan with safety scoring to guide improvements.

Can I use automated code review to check Effect-TS test coverage and error handling?

Yes, you can use automated code review to check Effect-TS test coverage and error handling. It discovers changed files, categorizes them, and launches specialized reviewers in parallel to produce a unified report highlighting Critical, Warning, and Info findings.

Does Effect-TS code review support parallel multi-agent assessment for PR diffs?

Effect-TS code review supports parallel multi-agent assessment for PR diffs. It orchestrates specialized reviewers to evaluate changed files across primitives, OTEL, error handling, tests, and UI quality, outputting an actionable remediation plan and scoring.

How does an Effect-TS code review report categorize findings and remediation steps?

An Effect-TS code review report categorizes findings into Critical, Warning, and Info levels across primitives, branded types, OTEL, error handling, tests, and UI quality. It supplies an actionable remediation plan and scoring to guide improvements across the codebase.

Why does my Effect-TS code review flag missing branded types and insufficient testing?

Your Effect-TS code review flags missing branded types and insufficient testing to enforce safety and compliance. It verifies code changes against Effect-TS primitives, identifies insufficient use of testing, and outputs a structured remediation plan to resolve these issues.