super-review:react

Detect React 18.3+ anti-patterns in component diffs during PR review.

Updated May 15, 2026
One-click install
npx skills add https://github.com/mattnowdev/super-review --skill super-review-react
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-review:react
Source: https://github.com/mattnowdev/super-review/tree/main/skills/react
Command: npx skills add https://github.com/mattnowdev/super-review --skill super-review-react

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents React anti-patterns from slipping into PRs by giving reviewers a focused, evidence-based checklist of issues that linters often miss.

Core Features & Use Cases

It targets correctness and frontend reliability risks in React 18.3+ code. It flags common sources of stale state, hydration mismatches, incorrect list keys, unsafe rendering assumptions, and broken React 19 features like use() and useActionState. It is used when reviewing diffs that touch React components, especially in client-side code paths.

Quick Start

Ask an AI reviewer to analyze the PR’s client-side React changes and report any checklist-matching anti-patterns with concrete evidence from the diff.

Frequently Asked Questions about super-review:react

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

FAQPage Schema
How do I catch subtle React hydration mismatches and useEffect anti-patterns in a PR?

You can catch React hydration mismatches and useEffect anti-patterns by applying an evidence-based checklist to component diffs, detecting stale state and incorrect list keys that linters often miss.

What React anti-patterns cause frontend state bugs that code review should flag?

Common React anti-patterns causing frontend state bugs include render-phase nondeterminism, broken subscription lifecycles, incorrect list keying, and unsafe async flows inside useEffect.

How do I review React 19 use() and useActionState usage for correctness?

To review React 19 use() and useActionState usage for correctness, analyze client-side component diffs against an evidence-anchored checklist to detect unsafe rendering assumptions and broken features.

Does this code review approach detect stale state in React 18.3+ components?

Yes, this code review approach detects stale state in React 18.3+ components by monitoring dependency-driven stack detection across useEffect async flows and subscription lifecycles.

What is the best way to prevent React list keying and event listener issues from merging?

The best way to prevent React list keying and event listener issues from merging is to run an AI reviewer on client-side changes to report matching anti-patterns with concrete diff evidence.