software-assembly-line

Analyze code changes for architectural compliance and system design integrity.

Review code and scripts to ensure Bun is used as the runtime, never tsx or node.

Review code for unnecessary complexity and adherence to YAGNI principles.

Review database migrations, data models, and code that manipulates persistent data.

Review @fm/web code to ensure zero usage of useState/useEffect, enforcing effect-atom patterns.

Review code for strict adherence to Effect-TS patterns and conventions.

Review code for proper import conventions: .ts extensions and correct package imports.

Analyze code for design patterns, anti-patterns, naming conventions, and code duplication.

Analyze code for performance issues, bottlenecks, and scalability concerns.

Comprehensive security audits and vulnerability assessments for code changes.

Review test code for 100% coverage compliance and proper Effect testing patterns.

Review code for zero tolerance on type suppressions and unsafe type patterns.

Document Effect-TS patterns discovered during implementation for future reuse.

Document cross-package integration patterns and how packages work together.

Document solutions to TypeScript type errors for future reference, especially complex scenarios that were solved without type suppressions.

Plan effect-atom state management for UI features, ensuring no useState/useEffect usage.

Review plans to ensure they can be implemented cleanly with Effect-TS patterns.

Review plans to identify all packages that will be affected and ensure the plan accounts for cross-package dependencies.

Assess whether a plan will require complex types or risk needing type suppressions.

Automatically creates blocks/blocked-by relationships between Linear issues based on layer tags and explicit dependencies.

Design Effect-TS service layers, dependency injection patterns, and layer composition for new features.

Parses a validated PRD to extract all entities (database tables, models) and their relationships. Outputs structured data for story generation.

Parses a validated PRD to extract all user flows, API endpoints, and UI components. Maps flows to implementation layers.

Analyze user stories to determine which architectural layers they touch, then auto-generate task dependencies (blocks/blocked-by relations).

Validates that a Product Requirements Document (PRD) contains all required sections for automated story generation.

When a feature requires database schema changes, map all downstream impacts across the monorepo.

Generates Linear user stories from extracted entities and flows. Assigns layer tags for automatic dependency ordering.

Plan comprehensive test coverage for features requiring 100% coverage.