extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
$ npx -y skills add facebook/react --skill flags --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/flagsContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
name: flags description: Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
Arguments:
| Option | Purpose | |--------|---------| | (none) | Show all flags across all channels | | `--diff <ch1> <ch2>` | Compare flags between channels | | `--cleanup` | Show flags grouped by cleanup status | | `--csv` | Output in CSV format |
✅ enabled, ❌ disabled, 🧪 `__VARIANT__`, 📊 profiling-only
1. Run `yarn flags $ARGUMENTS` 2. Explain the output to the user 3. For --diff, highlight meaningful differences
React is a JavaScript library for building user interfaces. Declarative: React makes it painless to create interactive UIs.
Repo: facebook/react
Use when adding new error messages to React, or seeing "unknown error code" warnings.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.