Extract Errors
Keeps React’s numbered invariant error catalog in sync when you add or change error messages in the facebook/react repository.
Overview
Extract-errors is an agent skill for the Build phase that runs React’s `yarn extract-errors` workflow and reports whether new invariant errors need codes or the registry is out of date.
Install
npx skills add https://github.com/facebook/react --skill extract-errorsWhat is this skill?
- Runs `yarn extract-errors` as the canonical update step for the error registry
- Surfaces new messages that still need assigned error codes
- Flags stale catalogs when you see “unknown error code” warnings during development
- Three-step checklist: extract, report new codes, verify registry is current
- 3-step instruction flow: run extract, report new codes, verify up to date
Adoption & trust: 1k installs on skills.sh; 246k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You changed React error messages but the numbered error-code table and CI warnings no longer match what ships in the bundle.
Who is it for?
Contributors working in facebook/react who add or edit `invariant` error strings and must keep the extract-errors pipeline green.
Skip if: App developers using React from npm who never run the monorepo toolchain—use framework docs and local debugging instead.
When should I use this skill?
Adding new error messages to React, or seeing "unknown error code" warnings.
What do I get? / Deliverables
After extraction you know which new errors lack codes and whether the published error-code list needs an update before merge.
- Report of new errors needing codes
- Confirmation that error codes match the extract-errors output
Recommended Skills
Journey fit
Error-code extraction runs while editing the React library source, which is core frontend build and maintenance work. The skill is tied to React UI runtime messages and the repo’s frontend packaging workflow, not shipping or growth tasks.
How it compares
A repo-specific maintainer checklist, not a general React debugging or testing skill.
Common Questions / FAQ
Who is extract-errors for?
React repository contributors and maintainers who touch error-message source and rely on Yarn-based monorepo scripts.
When should I use extract-errors?
During Build when adding new React error messages, after refactors that change invariant text, or when dev or CI warns about unknown error codes.
Is extract-errors safe to install?
It only documents running a standard project script; review the Security Audits panel on this page and treat it like any third-party skill before letting an agent run shell commands in your clone.
SKILL.md
READMESKILL.md - Extract Errors
# Extract Error Codes ## Instructions 1. Run `yarn extract-errors` 2. Report if any new errors need codes assigned 3. Check if error codes are up to date