Best for
- Always use this skill when writing audit scan commands - do not
Source profileQuality 68/100
github/awesome-copilot/skills/react-audit-grep-patterns/SKILL.md
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
- Source repository stars
- 37,126
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Complete scan command library for React 18.3.1 and React 19 migration audits.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/github/awesome-copilot --skill "skills/react-audit-grep-patterns"Safe inspection promptEditorial
Inspect the Agent Skill "react-audit-grep-patterns" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/react-audit-grep-patterns/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
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-sc…
references/react18-scans.md - all scans for React 16/17 → 18.3.1 auditreferences/react19-scans.md - all scans for React 18 → 19 auditreferences/test-scans.md - test file specific scans (used by both auditors) - 02
Base Patterns Used Across All Scans
Review the “Base Patterns Used Across All Scans” section in the pinned source before continuing.
Review and apply the “Base Patterns Used Across All Scans” source section. - 03
Standard flags used throughout:
Review the “Standard flags used throughout:” section in the pinned source before continuing.
Review and apply the “Standard flags used throughout:” source section.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 68/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 37,126 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- github/awesome-copilot
- Skill path
- skills/react-audit-grep-patterns/SKILL.md
- Commit
- 9933dcad5be5caeb288cebcd370eeeb2fc2f1685
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original 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 auditreferences/react19-scans.md- all scans for React 18 → 19 auditreferences/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
# 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"'
Alternatives
Compare before choosing
Computed 88234,327
affaan-m/ECC
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
Computed 81234,327
affaan-m/ECC
coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Computed 79234,327
affaan-m/ECC
coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Computed 76234,327
affaan-m/ECC
project-guidelines-example
Project-specific skill template covering architecture, patterns, testing, and deployment guidance.