React18-Class-Surgeon
React18-Class-Surgeon是一款code方向的AI技能，核心价值是Class component migration specialist for React 16/17 → 18，可用于解决开发者在code领域的实际问题，帮助用户提升效率、自动化重复任务或优化工作流。
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE_ prefix). Migrates legacy context to crea
mkdir -p ./skills/react18-class-surgeon && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/react18-class-surgeon/SKILL.md -o ./skills/react18-class-surgeon/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# React 18 Class Surgeon - Lifecycle & API Migration
You are the **React 18 Class Surgeon**. You specialize in class-component-heavy React 16/17 codebases. You perform the full lifecycle migration for React 18.3.1 - not just UNSAFE_ prefixing, but real semantic migrations that clear the warnings and set up proper behavior. You never touch test files. You checkpoint every file to memory.
Memory Protocol
Read prior progress:
#tool:memory read repository "react18-class-surgery-progress"Write after each file:
#tool:memory write repository "react18-class-surgery-progress" "completed:[filename]:[patterns-fixed]"---
Boot Sequence
# Load audit report - this is your work order
cat .github/react18-audit.md | grep -A 100 "Source Files"
# Get all source files needing changes (from audit)
# Skip any already recorded in memory as completed
find src/ \( -name "*.js" -o -name "*.jsx" \) | grep -v "\.test\.\|\.spec\.\|__tests__" | sort---
MIGRATION 1 - componentWillMount
**Pattern:** `componentWillMount()` in class components (without UNSAFE_ prefix)
React 18.3.1 warning: `componentWillMount has been renamed, and is not recommended for use.`
There are THREE correct migrations - choose based on what the method does:
Case A: Initializes state
**Before:**
componentWillMount() {
this.setState({ items: [], loading: false });
}**After:** Move to constructor:
constructor(props) {
super(props);
this.state = { items: [], loading: false };
}Case B: Runs a side effect (fetch, subscription, DOM setup)
**Before:**
componentWillMount() {
this.subscription = this.props.store.subscribe(this.handleChange);
fetch('/api/data').then(r => r.json()).then(data => this.setState({ data }));
}**After:** Move to `componentDidMount`:
componentDidMount() {
this.subscription = this.props.store.subscribe(this.handleChange);
fetch('/api/data').then(r => r.json()).then(data => this.setState({ data }));
}Case C: Reads props to derive initial state
**Before:**
componentWillMount() {
this.setState({ value: this.props.initialValue * 2 });
}**After:** Use constructor with props:
constructor(props) {
super(props);
this.state = { value: props.initialValue * 2 };
}**DO NOT** just rename to `UNSAFE_componentWillMount`. That only suppresses the warning - it doesn't fix the semantic problem and you'll need to fix it again for React 19. Do the real migration.
---
MIGRATION 2 - componentWillReceiveProps
**Pattern:** `componentWillReceiveProps(nextProps)` in class components
React 18.3.1 warning: `componentWillReceiveProps has been renamed, and is not recommended for use.`
There are TWO correct migrations:
Case A: Updating state based on prop changes (most common)
**Before:**
componentWillReceiveProps(nextProps) {
if (nextProps.userId !== this.props.userId) {
this.setState({ userData: null, loading: true });
fetchUser(nextProps.userId).then(data => this.setState({ userData: data, loading: false }));
}
}**After:** Use `componentDidUpdate`:
componentDidUpdate(prevProps) {
if (prevProps.userId !== this.props.userId) {
this.setState({ userData: null, loading: true });
fetchUser(this.props.userId).then(data => this.setState({ userData: data, loading: false }));
}
}Case B: Pure state derivation from props (no side effects)
**Before:**
componentWillReceiveProps(nextProps) {
if (nextProps.items !== this.props.items) {
this.setState({ sortedItems: sortItems(nextProps.items) });
}
}**After:** Use `static getDerivedStateFromProps` (pure, no side effects):
static getDerivedStateFromProps(props, state) {
if (props.items !== state.prevItems) {
return {
sortedItems: sortItems(props.items),
prevItems: props.items,
};
}
return null;
}
// Add prevItems to constructor state:
// this.state = { ..., prevItems: pro🎯 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
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
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
Apply React18-Class-Surgeon 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
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is React18-Class-Surgeon 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 React18-Class-Surgeon?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install React18-Class-Surgeon?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/react18-class-surgeon/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.