facebook/react
7 skills8.5k installs2M starsGitHub
Install
npx skills add https://github.com/facebook/reactSkills in this repo
1FixThe fix skill resolves lint errors and formatting issues in the React repository before commits so changes pass continuous integration. Instructions are minimal and deterministic: run yarn prettier to fix formatting on changed files, then run yarn linc to surface remaining lint problems, and report any manual fixes still required. Common mistakes are called out explicitly. yarn prettier only formats changed files, not the entire tree. Ignoring linc errors will fail CI, so they must be resolved before committing. The skill targets the Facebook React monorepo workflow rather than generic ESLint setup. It assumes yarn scripts exist and that contributors run both commands as a pre-commit hygiene step. No additional configuration or custom rules are documented in the skill itself. Contributors should run both yarn commands before every commit. See SKILL.md for the authoritative workflow and constraints.2.1kinstalls2Extract ErrorsThe extract-errors skill use when adding new error messages to React, or seeing "unknown error code" warnings. # 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 # 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 Use when adding new error messages to React, or seeing "unknown error code" warnings. Use when adding new error messages to React, or seeing "unknown error code" warnings. Follow the SKILL.md workflow for extract-errors: prerequisites, command steps, validation checks, common failure modes, and reference examples that keep outputs aligned with upstream project conventions. Refer to SKILL.md reference sections for configuration, troubleshooting, and worked examples.1.2kinstalls3TestThe test skill use when you need to run tests for React core Supports source www stable and experimental channels Run tests for the React codebase Arguments ARGUMENTS Channel flags and test pattern Usage Examples test ReactFiberHooks Run with source channel default test experimental ReactFiberHooks Run with experimental channel test www ReactFiberHooks Run with www-modern channel test www variant false ReactFiberHooks Test __VARIANT__ false test stable ReactFiberHooks Run with stable channel test classic ReactFiberHooks Run with www-classic channel test watch ReactFiberHooks Run in watch mode TDD Release Channels default Source canary channel uses ReactFeatureFlags js defaults experimental Source experimental channel with __EXPERIMENTAL__ flags true www www-modern channel with __VARIANT__ flags true www variant false www channel with __VARIANT__ flags false stable What ships to npm classic Legacy www-classic rarely needed Instructions 1 Parse channel from arguments default source 2 Map to yarn command default yarn test silent no-watchman pattern experimental yarn test r experimental silent no-watchman pattern stable yarn test-stable silent no-watchman pattern classic yarn test-cla.1.1kinstalls4VerifyThe verify skill use when you want to validate changes before committing or when you need to check all React contribution requirements Verification Run all verification steps Arguments ARGUMENTS Test pattern for the test step Instructions Run these first in sequence 1 Run yarn prettier format code stop if fails 2 Run yarn linc lint changed files stop if fails Then run these with subagents in parallel 1 Use flow to type check stop if fails 2 Use test to test changes in source stop if fails 3 Use test www to test changes in www stop if fails If all pass show success summary On failure stop immediately and report the issue with suggested fixes Verification Run all verification steps Arguments ARGUMENTS Test pattern for the test step Instructions Run these first in sequence 1 Run yarn prettier format code stop if fails 2 Run yarn linc lint changed files stop if fails Then run these with subagents in parallel 1 Use flow to type check stop if fails1.1kinstalls5Feature FlagsThe feature-flags skill guides React core contributors and framework maintainers working with React feature flag tests and @gate pragmas. It documents flag file locations, channel-specific test expectations, and procedures for adding or updating flags when tests fail across experimental channels. Agents help diagnose gate pragma mismatches, update snapshot tests, and understand which flags apply to which release channels. The skill is scoped to the facebook/react repository flag infrastructure rather than general app feature toggles. React core feature flag test debugging and updates. @gate pragma and channel-specific test failure guidance. Flag file locations and add-new-flag procedures. Scoped to facebook/react repository flag infrastructure. Helps maintainers fix experimental channel test failures. Debug and update React feature flag tests, @gate pragmas, and channel-specific flag behavior.1.1kinstalls6Flowflow is an official skill from facebook/react that instructs agents to run yarn flow with a renderer argument—dom-node by default, or dom-browser, native, and fabric for platform-specific code. It reports type errors with file locations and supports comprehensive CI checks via yarn flow-ci when slower full validation is needed. Developers reach for flow when Flow type errors appear in React code or when validating renderer-specific changes in the React monorepo. The skill prevents common mistakes like running Flow without specifying a renderer.1kinstalls7Flagsflags is an agent skill from facebook/react for checking feature flag states, comparing release channels, and debugging why features behave differently across builds. Options include showing all flags across channels, --diff between two channels, --cleanup grouped by cleanup status, and --csv CSV export. Documented channels span www and www-modern for Meta internal, canary, next, and experimental for OSS, plus rn, rn-fb, and rn-next for React Native. A legend marks enabled, disabled, __VARIANT__, and profiling-only flags. Developers reach for flags when a React or React Native feature works on one channel but not another and they need a structured flag inventory instead of manual source grep.970installs