react-critic

Identify React component and upgrade risks with evidence-backed findings.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zivtech/react-critic --skill react-critic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-critic
Source: https://github.com/zivtech/react-critic/tree/main/.claude/skills/react-critic
Command: npx skills add https://github.com/zivtech/react-critic --skill react-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

React codebases commonly suffer from subtle correctness, performance, and upgrade risks that slip through ad-hoc reviews. This skill defines a rigorous, evidence-driven critique workflow to surface issues and actionable improvements.

Core Features & Use Cases

  • Enforces a harsh-critic style rubric for React plans, components, and migrations.
  • Requires concrete evidence for major findings and supports audience-specific perspectives (Security, New-hire, Ops).
  • Useful for code reviews, upgrade planning, and plan-first assessments across React, Next.js, and React Native.

Quick Start

Provide a strict verdict on a React plan or code and return evidence-backed findings.

Frequently Asked Questions about react-critic

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

FAQPage Schema
How do I review React components for performance and security risks?

You identify React component risks by enforcing a strict critique rubric requiring concrete evidence for major findings. This process surfaces hooks usage, state ownership, and security vulnerabilities while tailoring perspectives to audiences like Ops or new-hires.

What is the best way to assess a React migration plan before upgrading?

Assess React migration plans by applying an evidence-driven critique workflow that exposes upgrade risks. This approach evaluates plans across React, Next.js, and React Native, providing a strict verdict and actionable improvements backed by explicit evidence.

Can I use this approach to review React Native and Next.js codebases?

Yes, the rigorous critique workflow applies to reviews across React, Next.js, and React Native. It enforces a harsh-critic style rubric to evaluate hooks usage, state ownership, and migration plans while requiring structured outputs for major findings.

How do I enforce evidence-backed findings during a React code review?

Enforce evidence-backed findings by demanding concrete evidence for all CRITICAL and MAJOR issues identified during the review. The workflow rejects ad-hoc assessments, requiring structured outputs that expose subtle correctness and performance risks.

Why does my React code review miss subtle correctness and upgrade risks?

Ad-hoc reviews miss subtle React risks because they lack a rigorous, evidence-driven critique workflow. Implementing a strict rubric surfaces these hidden component and migration vulnerabilities using explicit, structured evidence.