What problem does it solve? Reviewing Remix v2 pull requests consistently is hard because issues span routing, loaders/actions, forms, error boundaries, SSR performance, and session handling, and reviewers often miss areas or apply conventions from React Router v7 or Next.js by mistake. ## Core Features & Use Cases - Six-Area Coverage: Loads dedicated review skills for routing, data flow, forms, error boundaries, SSR/performance, and meta/sessions so no area is skipped. - Parallel or Sequential Execution: Fans out one subagent per area when the agent supports subagents, or runs the same areas sequentially with identical output. - Evidence-Gated Findings: Requires every Critical/Major finding to cite a verified FILE:LINE with concrete artifacts, filtering out style preferences and false positives. - Use Case: Before merging a Remix v2 feature branch, run the review to get a severity-ranked report with a Ready verdict, then re-run after fixes with lint, typecheck, and tests. ## Quick Start Ask the agent to review the current branch's Remix v2 changes against main and produce a severity-ranked report with a ready verdict.