Agent skill · Security

react-audit-grep-patterns

Provides the complete, verified grep scan command library for auditing React codebases before a React 18.3.1 or React 19 upgrade. Use this skill whenever running a migration audit - for both the react18-auditor and react19-auditor agents. Contains every grep pattern needed to find deprecated APIs, removed APIs, unsafe lifecycle methods, batching vulnerabilities, test file issues, dependency conflicts, and React 19 specific removals. Always use this skill when writing audit scan commands - do not rely on memory for grep syntax, especially for the multi-line async setState patterns which require

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill react-audit-grep-patterns --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 5
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/react-audit-grep-patterns/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# React Audit Grep Patterns Complete scan command library for React 18.3.1 and React 19 migration audits. ## Usage Read the relevant section for your target: - **`references/react18-scans.md`** - all scans for React 16/17 → 18.3.1 audit - **`references/react19-scans.md`** - all scans for React 18 → 19 audit - **`references/test-scans.md`** - test file specific scans (used by both auditors) - **`references/dep-scans.md`** - dependency and peer conflict scans ## Base Patterns Used Across All Scans ```bash # Standard flags used throughout: # -r = recursive # -n = show line numbers # -l = show filenames only (for counting affected files) # --include="*.js" --include="*.jsx" = JS/JSX files only # | grep -v "\.test\.\|\.spec\.\|__tests__" = exclude test files # | grep -v "node_modules" = safety (usually handled by not scanning node_modules) # 2>/dev/null = suppress "no files found" errors # Source files only (exclude tests): SRC_FLAGS='--include="*.js" --include="*.jsx"' EXCLUDE_TESTS='grep -v "\.test\.\|\.spec\.\|__tests__"' # Test files only: TEST_FLAGS='--include="*.test.js" --include="*.test.jsx" --include="*.spec.js" --include="*.spec.jsx"' ```

What's inside
Steps it walks through
  1. Usage
  2. Base Patterns Used Across All Scans
Ships with 4 files
  • references/dep-scans.md
  • references/react18-scans.md
  • references/react19-scans.md
  • references/test-scans.md
Commands it runs
Standard flags used throughout:
Source files only (exclude tests):
Test files only:
More from awesome-copilot
All skills →
About this skill
What does the react-audit-grep-patterns skill do?

Provides the complete, verified grep scan command library for auditing React codebases before a React 18.3.1 or React 19 upgrade. Use this skill whenever running a migration audit - for both the react18-auditor and react19-auditor agents. Contains every grep pattern needed to find deprecated APIs, removed APIs, unsafe lifecycle methods, batching vulnerabilities, test file issues, dependency conflicts, and React 19 specific removals. Always use this skill when writing audit scan commands - do not rely on memory for grep syntax, especially for the multi-line async setState patterns which require

How do I install it?

Run `npx skills add github/awesome-copilot --skill react-audit-grep-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going