react-reviewer

name	react-reviewer
description	Review React components, hooks, state, rendering, accessibility, Server Components, testing, and performance.
version	1.0.0
since	2026-08-29
last_modified	2026-08-29
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.0.0","date":"2026-08-29","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

React Reviewer

Purpose

Review React applications for hooks correctness, component composition, prop drilling elimination, memoisation discipline, Context API usage, concurrent features, Server Components, accessibility, and React 18 best practices. Treat regulatory, security, and operational references as review and evidence guidance, not legal advice.

Goal and behavioral contract

The authoritative Goal and artifact references are defined in descriptor.yaml. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in contract.yaml. MCP/A2A trust boundaries and the reviewed execution closure live in integrations/ and dependencies.yaml; ASPS and assurance requirements live in assurance.yaml.

Treat those declarations as mandatory execution constraints. skcr validates requirements but does not claim verification or enforce them at runtime.

When to use

• React best practices decisions, controls, or operating practices need independent review.
• A change affects React best practices artifacts such as React component and JSX, hook implementation and dependency array, Context or state management definition, React.memo or useMemo or useCallback usage, React Server Component boundary, accessibility attribute and ARIA usage in JSX.
• The user needs evidence-oriented findings for risks such as stale closure in useEffect dependency array causing incorrect behaviour, unnecessary re-render from object or array literal created inline in JSX, useEffect used for data fetching without cleanup or cancellation, Context triggering full subtree re-render on every value change, React.memo or useMemo applied without profiling confirming render cost, key prop using array index causing DOM reconciliation errors on list reorder.
• Audit, security, operations, or platform stakeholders need a concise readiness position.
• Existing documentation, tickets, tests, or logs must be turned into actionable remediation items.

Operating model

1. Identify the relevant React best practices artifacts, owners, systems, environments, and review boundary.
2. Compare the available artifacts against expected signals such as React DevTools Profiler flame graph, ESLint react-hooks plugin exhaustive-deps warning, render count measurement with Why Did You Render, bundle analysis with Webpack Bundle Analyzer or Vite rollup output, Accessibility audit with axe-core or React Testing Library queries, React Server Component serialisation error or client boundary audit.
3. Separate confirmed gaps from assumptions, missing evidence, and advisory improvement opportunities.