test
react/react · Agent Skill
Runs tests for the React codebase, supporting various channels and execution modes.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | react/react ↗ |
| Skill folder | test |
| Stars | 249,163 |
| Bundled files | 1 |
| License | MIT |
| Last updated | January 23, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “test” skill from mozgi.io (https://mozgi.io/skills/test/) for me. 1. Download the archive: https://mozgi.io/skills/test/download If it fails, take the skill folder from the source: https://github.com/react/react/tree/main/.claude/skills/test 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “test” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/test/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/react/react.git /tmp/react mkdir -p .claude/skills cp -r /tmp/react/.claude/skills/test .claude/skills/test
Restart Claude Code — the skill appears in the list; call it manually with /test. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/react/react.git /tmp/react mkdir -p .agents/skills cp -r /tmp/react/.claude/skills/test .agents/skills/test
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $test. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/react/react.git /tmp/react mkdir -p .cursor/skills cp -r /tmp/react/.claude/skills/test .cursor/skills/test
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/react/react.git /tmp/react mkdir -p .gemini/skills cp -r /tmp/react/.claude/skills/test .gemini/skills/test
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyRun 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 defaultsexperimental- Source/experimental channel with __EXPERIMENTAL__ flags = truewww- www-modern channel with __VARIANT__ flags = truewww variant false- www channel with __VARIANT__ flags = falsestable- What ships to npmclassic- 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-classic --silent --no-watchman <pattern> - www →
yarn test-www --silent --no-watchman <pattern> - www variant false →
yarn test-www --variant=false --silent --no-watchman <pattern>
3. Report test results and any failures
Hard Rules:
1. Use --silent to see failures - This limits the test output to only failures.
2. Use --no-watchman - This is a common failure in sandboxing.
Common Mistakes:
- Running without a pattern - Runs ALL tests, very slow. Always specify a pattern.
- Forgetting both www variants - Test
wwwANDwww variant falsefor__VARIANT__flags. - Test skipped unexpectedly - Check for
@gatepragma; seefeature-flagsskill.
Frequently asked questions
What does the test skill do?
Runs tests for the React codebase, supporting various channels and execution modes.
How do I install test?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with test?
Skills are plain Markdown instructions (the Agent Skills format), so test works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is test free?
The skill is published openly by react under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.