PromptCreek
Sign up
Back to Skills
Engineering

Test

Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.

$ npx promptcreek add test

Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

This skill executes tests for a React codebase, allowing users to specify the channel (source, experimental, stable, classic, or www) and a test pattern. It's designed for developers who need to validate their code changes against different React environments and configurations.

When to Use

  • Validate a bug fix in the stable release channel.
  • Test a new feature with experimental flags enabled.
  • Verify code changes against the www-modern channel.
  • Run tests in watch mode during development (TDD).
  • Confirm compatibility with legacy www-classic.
  • Check for regressions after refactoring code.

Key Features

Supports multiple release channels (source, experimental, stable, classic, www).
Allows specifying a test pattern to run specific tests.
Uses `--silent` flag to limit output to failures.
Uses `--no-watchman` to avoid sandboxing issues.
Provides examples for common usage scenarios.
Offers guidance on common mistakes to avoid.

Installation

Run in your project directory:
$ npx promptcreek add test

Auto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.

View Full Skill Content

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:

  • Parse channel from arguments (default: source)
  • Map to yarn command:

- (default) → yarn test --silent --no-watchman

- experimental → yarn test -r=experimental --silent --no-watchman

- stable → yarn test-stable --silent --no-watchman

- classic → yarn test-classic --silent --no-watchman

- www → yarn test-www --silent --no-watchman

- www variant false → yarn test-www --variant=false --silent --no-watchman

  • Report test results and any failures

Hard Rules:

  • Use --silent to see failures - This limits the test output to only failures.
  • 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 www AND www variant false for __VARIANT__ flags.
  • Test skipped unexpectedly - Check for @gate pragma; see feature-flags skill.
0Installs
0Views

Supported Agents

Claude CodeCursorCodexGemini CLIAiderWindsurfOpenClaw

Attribution

facebook
facebook/react
MITadmin

Details

License
MIT
Source
admin
Published
3/18/2026

Tags

.claude

Related Skills

Agent Protocol

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.

90
Alireza Rezvani
#c-level#c-level advisor

Agent Workflow Designer

Agent Workflow Designer

20
Alireza Rezvani
#engineering

CTO Advisor

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

20
Alireza Rezvani
#c-level#c-level advisor