Automated summary
Checks React feature flag states, compares release channels, and exports data as CSV.
Strengths
- Single command overview of all flags across channels
- Accurate channel-to-channel diff with --diff
- Flags grouped by cleanup status for prioritization
- CSV export for external analysis
Limitations
- Requires a local React repo set up with yarn
- Does not cover dynamic or server-side flags
- __VARIANT__ flags can be ambiguous without additional context
When you need to diagnose why a feature behaves differently across React release channels or plan flag cleanup.
If you are working on a non-React project or lack access to React's flag infrastructure.
Security analysis
SafeThe skill instructs running a local 'yarn flags' command to query feature flag states, with no destructive, exfiltrating, or network-dependent actions. It poses no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Show all React feature flags across every channel (www, canary, next, experimental, rn, etc.) and explain the legend.Compare React feature flags between the canary and experimental channels using --diff and highlight the meaningful differences.List all React flags grouped by cleanup status and output as CSV.name: flags description: Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
Feature Flags
Arguments:
- $ARGUMENTS: Optional flags
Options
| 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 |
Channels
www,www-modern- Meta internalcanary,next,experimental- OSS channelsrn,rn-fb,rn-next- React Native
Legend
✅ enabled, ❌ disabled, 🧪 __VARIANT__, 📊 profiling-only
Instructions
- Run
yarn flags $ARGUMENTS - Explain the output to the user
- For --diff, highlight meaningful differences
Common Mistakes
- Forgetting
__VARIANT__flags - These are tested both ways in www; check both variants - Comparing wrong channels - Use
--diffto see exact differences
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/react-feature-flags-checker-mm8o52h0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/react-feature-flags-checker-mm8o52h0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/react-feature-flags-checker-mm8o52h0/download' --output '.skill-downloads/react-feature-flags-checker-mm8o52h0/SKILL.md.part' && mv '.skill-downloads/react-feature-flags-checker-mm8o52h0/SKILL.md.part' '.skill-downloads/react-feature-flags-checker-mm8o52h0/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/react-feature-flags-checker-mm8o52h0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.