extract-errors

Identify missing React error codes and update the registry via yarn extract-errors.

247k|51.2k|Updated May 24, 2013
One-click install
npx skills add https://github.com/facebook/react --skill extract-errors-facebook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-errors
Source: https://github.com/facebook/react/tree/main/.claude/skills/extract-errors
Command: npx skills add https://github.com/facebook/react --skill extract-errors-facebook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers and developers ensure every new error message in React has a corresponding error code, reducing "unknown error code" warnings and enabling consistent diagnostics.

Core Features & Use Cases

  • Error code auditing: Detects missing or duplicate error codes as new messages are added.
  • Codebase governance: Integrates into development workflows to review and assign codes during code reviews or CI checks.
  • Use Case: When introducing a new error message, run this Skill to verify a proper code exists and update the registry if needed.

Quick Start

Run yarn extract-errors to scan for unassigned error codes and report any discrepancies.

Frequently Asked Questions about extract-errors

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

FAQPage Schema
How do I assign missing React error codes for new error messages?

To assign missing React error codes, run the local extraction workflow via yarn extract-errors to scan the codebase, identify unassigned messages, and update the registry accordingly.

Why does React show an unknown error code warning during development?

An unknown error code warning appears during React development when a new error message is introduced without a corresponding entry in the error code registry. Running extract-errors detects and resolves these discrepancies.

Can I check for missing React error codes during a CI pipeline?

Yes, you can integrate React error code auditing into CI checks to automatically detect missing or duplicate codes when new error messages are added, ensuring consistent diagnostics across builds.

What is the best way to audit duplicate error codes in a React codebase?

The best way to audit duplicate React error codes is running the extract-errors workflow, which scans for missing or duplicate codes and reports discrepancies to maintain codebase governance.

How do I review new React error codes during a code review?

To review new React error codes during code reviews, run the extract-errors workflow to verify a proper code exists for each new message and update the registry if needed before merging.