A local-first development skill designed to review React and TypeScript components for correctness, hook safety, prop modeling, and accessibility with minimal, precise changes.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install react-component-review
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install react-component-review using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
React Component Review is a standalone development skill tailored for engineers seeking rigorous code quality checks without leaving their local environment. It systematically analyzes React and TypeScript components, identifying hook-dependency risks, rendering inefficiencies, state coverage gaps, and screen-reader accessibility issues. Operating fully offline, it provides high-value static and behavioral assessments without requiring external dependencies.
By leveraging this tool within Openclaw Skills, teams can ensure their UI blocks adhere to strict engineering principles. The skill prioritizes surgical, non-breaking modifications, ensuring that generated patches fix underlying structural or behavioral flaws while preserving intended component execution.
This skill operates natively as a local-first, standalone tool requiring no primary cloud infrastructure configuration. To run Openclaw Skills with enhanced capabilities and workspace context via the optional cloud CLI layer, execute the following commands:
npm install -g @ritualai/cli
ritual init
ritual status
The skill runs locally and manages architectural insights through an optional knowledge capture layer using the Open Knowledge Format (OKF). Upon user approval, durable engineering rules are structured and written to the repository.
All approved knowledge components are stored in the following structure:
knowledge/engineering/<slug>.md
Each generated markdown file contains YAML frontmatter utilizing the following schema structure:
| Field | Type | Description |
|---|---|---|
type |
String | Categorization of knowledge (e.g., API Convention, Component Pattern). |
title |
String | A brief, single-line explanation of the rule. |
description |
String | Context around what was learned during the review task. |
resource |
String | Local filepath referencing the evidence or component reviewed. |
tags |
Array | Metadata tags for categorization and search filtering. |
timestamp |
String | ISO 8601 formatted date and time of the file creation. |
Loading
A local-first development skill to check keyboard accessibility, screen-reader semantics, contrast, focus states, and dynamic announcements on any UI surface.

A local-first development skill that audits codebases for robust error paths, input boundaries, timeout configurations, structured logging, and operation idempotency.

An on-demand, pay-per-call compliance toolkit enabling AI agents to screen entities against global watchlists, sanctions, and PEP databases instantly.

A local-first development skill to audit and ensure proper loading, error, empty, partial, and retry states across UI surfaces.

A structured workflow for AI agents to systematically isolate and triage system performance issues using concrete telemetry data.

An automated development skill that reviews API diffs for compatibility, security, and schema evolution, classifying changes as additive, behavior-changing, or breaking.








































