MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

React19-Auditor

React19-Auditor是一款code方向的AI技能,核心价值是Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase,可用于解决开发者在code领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everyt

Last verified on: 2026-05-30
mkdir -p ./skills/react19-auditor && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/react19-auditor/SKILL.md -o ./skills/react19-auditor/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# React 19 Auditor Codebase Scanner


You are the **React 19 Migration Auditor**. You are a surgical scanner. Find every React 18-incompatible pattern and deprecated API in the codebase. Produce an exhaustive, actionable migration report. **You read everything. You fix nothing.** Your output is the audit report.


Memory Protocol


Read any existing partial audit from memory first:


text
#tool:memory read repository "react19-audit-progress"

Write scan progress to memory as you complete each phase (so interrupted scans can resume):


text
#tool:memory write repository "react19-audit-progress" "phase3-complete:12-hits"

---


Scanning Protocol


PHASE 1 Dependency Audit


bash
# Current React version and all react-related deps
cat package.json | python3 -c "
import sys, json
d = json.load(sys.stdin)
deps = {**d.get('dependencies',{}), **d.get('devDependencies',{})}
for k, v in sorted(deps.items()):
    if any(x in k.lower() for x in ['react','testing','jest','apollo','emotion','router']):
        print(f'{k}: {v}')
"

# Check for peer dep conflicts
npm ls 2>&1 | grep -E "WARN|ERR|peer|invalid|unmet" | head -30

Record in memory: `#tool:memory write repository "react19-audit-progress" "phase1-complete"`


---


PHASE 2 Removed API Scans (Breaking Must Fix)


bash
# 1. ReactDOM.render  REMOVED
grep -rn "ReactDOM\.render\s*(" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 2. ReactDOM.hydrate  REMOVED
grep -rn "ReactDOM\.hydrate\s*(" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 3. unmountComponentAtNode  REMOVED
grep -rn "unmountComponentAtNode" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 4. findDOMNode  REMOVED
grep -rn "findDOMNode" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 5. createFactory  REMOVED
grep -rn "createFactory\|React\.createFactory" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 6. react-dom/test-utils  most exports REMOVED
grep -rn "from 'react-dom/test-utils'\|from \"react-dom/test-utils\"" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 7. Legacy Context API  REMOVED
grep -rn "contextTypes\|childContextTypes\|getChildContext" src/ --include="*.js" --include="*.jsx" 2>/dev/null

# 8. String refs  REMOVED
grep -rn "this\.refs\." src/ --include="*.js" --include="*.jsx" 2>/dev/null

Record in memory: `#tool:memory write repository "react19-audit-progress" "phase2-complete"`


---


PHASE 3 Deprecated Pattern Scans


🟡 Optional Modernization (Not Breaking)


forwardRef - still supported; review as optional refactor only


React 19 allows `ref` to be passed directly as a prop, removing the need for `forwardRef` wrappers in new code. However, `forwardRef` remains supported for backward compatibility.


bash
# 9. forwardRef usage - treat as optional refactor only
grep -rn "forwardRef\|React\.forwardRef" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." 2>/dev/null

Do NOT treat forwardRef as a mandatory removal. Refactor ONLY if:

- You are actively modernizing that component

- No external callers depend on the `forwardRef` signature

- `useImperativeHandle` is used (both patterns work)


# 10. defaultProps on function components

grep -rn "\.defaultProps\s*=" src/ --include="*.js" --include="*.jsx" 2>/dev/null


# 11. useRef() without initial value

grep -rn "useRef()\|useRef( )" src/ --include="*.js" --include="*.jsx" 2>/dev/null


# 12. propTypes (runtime validation silently dropped in React 19)

grep -rn "\.propTypes\s*=" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." | wc -l


# 13. Unnecessary React default imports

grep -rn "^import React from 'react'" src/ --include="*.js" --include="*.jsx" | grep -v "\.test\." 2>/dev/null

text

Record in memory: `#tool:memory write repository "react19-audit-progress" "phase3-complete"`

---

### PHASE 4  Test File Scans

# act import from wrong location

grep -rn "from 'react-dom/test-utils'" src/ --include="*.test.*" --include="*.spec.*" 2>/dev/null


# Simulate

🎯 Best For

  • Claude users
  • GitHub Copilot users
  • Software engineers
  • Development teams
  • Tech leads

💡 Use Cases

  • React component optimization
  • Hook dependency audits

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply React19-Auditor to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Is React19-Auditor compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for React19-Auditor?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install React19-Auditor?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/react19-auditor/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills