Upgrade React applications to latest versions, migrate class components to hooks, and adopt concurrent features.
Works with
Covers version upgrade paths (React 16→17→18) with breaking changes, class-to-hooks migration patterns, and concurrent features like Suspense, transitions, and automatic batching
Includes ready-to-run codemods for automating unsafe lifecycle renames, import updates, and class-to-function conversions
Demonstrates performance optimization techniques using useMemo, useCallbac
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionreact-modernizationExecute the skills CLI command in your project's root directory to begin installation:
Fetches react-modernization from wshobson/agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate react-modernization. Access via /react-modernization in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
33.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
33.1K
stars
Master React version upgrades, class to hooks migration, concurrent features adoption, and codemods for automated transformation.
Breaking Changes by Version:
React 17:
React 18:
// Before: Class component
class Counter extends React.Component {
constructor(props) {
super(props);
this.state = {
count: 0,
name: "",
};
}
increment = () => {
this.setState({ count: this.state.count + 1 });
};
render() {
return (
<div>
<p>Count: {this.state.count}</p>
<button onClick={this.increment}>Increment</button>
</div>
);
}
}
// After: Functional component with hooks
function Counter() {
const [count, setCount] = useState(0);
const [name, setName] = useState("");
const increment = () => {
setCount(count + 1);
};
return (
<div>
<p>Count: {count}</p>
<button onClick={increment}>Increment</button>
</div>
);
}
// Before: Lifecycle methods
class DataFetcher extends React.Component {
state = { data: null, loading: true };
componentDidMount() {
this.fetchData();
}
componentDidUpdate(prevProps) {
if (prevProps.id !== this.props.id) {
this.fetchData();
}
}
componentWillUnmount() {
this.cancelRequest();
}
fetchData = async () => {
const data = await fetch(`/api/${this.props.id}`);
this.setState({ data, loading: false });
};
cancelRequest = () => {
// Cleanup
};
render() {
if (this.state.loading) return <div>Loading...</div>;
return <div>{this.state.data}</div>;
}
}
// After: useEffect hook
function DataFetcher({ id }) {
const [data, setData] = useState(null);
const [loading, setLoading] = useState(true);
useEffect(() => {
let cancelled = false;
const fetchData = async () => {
try {
const response = await fetch(`/api/${id}`);
const result = await response.json();
if (!cancelled) {
setData(result);
setLoading(false);
}
} catch (error) {
if (!cancelled) {
console.error(error);
}
}
};
fetchData();
// Cleanup function
return () => {
cancelled = true;
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
asyrafhussin/agent-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
I recommend react-modernization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
react-modernization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
react-modernization reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added react-modernization from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in react-modernization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: react-modernization is the kind of skill you can hand to a new teammate without a long onboarding doc.
react-modernization is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in react-modernization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
react-modernization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend react-modernization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 66