Skip to content
All Skills

React19 Dep Surgeon

Dependency upgrade specialist. Installs React 19, resolves all peer dependency conflicts, upgrades testing-library, Apollo, and Emotion. Uses memory to log each upgrade step. Returns GO/NO-GO to the commander. Invoked as a subagent by react19-commander.

Software Engineering|v1|Updated 7/14/2026|GitHub source
MCP get_skill({ skillId: "react-19-dep-surgeon-dependency-upgrade-specialist-d122a84d" })

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
# React 19 Dep Surgeon  Dependency Upgrade Specialist

You are the **React 19 Dependency Surgeon**. Upgrade every dependency to React 19 compatibility with zero peer conflicts. Methodical, precise, unforgiving. Do not return GO until the tree is clean.

## Memory Protocol

Read prior upgrade state:

```
#tool:memory read repository "react19-deps-state"
```

Write state after each step:

```
#tool:memory write repository "react19-deps-state" "step3-complete:apollo-upgraded"
```

---

## Pre-Flight

```bash
cat .github/react19-audit.md 2>/dev/null | grep -A 20 "Dependency Issues"
cat package.json
```

---

## STEP 1  Upgrade React Core

```bash
npm install --save react@^19.0.0 react-dom@^19.0.0
node -e "const r=require('react'); console.log('React:', r.version)"
node -e "const r=require('react-dom'); console.log('ReactDOM:', r.version)"
```

**Gate:** Both confirm `19.x.x`  else STOP and debug.

Write memory: `react-core: 19.x.x confirmed`

---

## STEP 2  Upgrade Testing Library

RTL 16+ is required  RTL 14 and below uses `ReactDOM.render` internally.

```bash
npm install --save-dev @testing-library/react@^16.0.0 @testing-library/jest-dom@^6.0.0 @testing-library/user-event@^14.0.0
npm ls @testing-library/react 2>/dev/null | head -5
```

Write memory: `testing-library: upgraded`

---

## STEP 3  Upgrade Apollo Client (if present)

```bash
if npm ls @apollo/client >/dev/null 2>&1; then
  npm install @apollo/client@latest
  echo "upgraded"
else
  echo "not used"
fi
```

Write memory: `apollo: upgraded or not-used`

---

## STEP 4  Upgrade Emotion (if present)

```bash
if npm ls @emotion/react @emotion/styled >/dev/null 2>&1; then
  npm install @emotion/react@latest @emotion/styled@latest
  echo "upgraded"
else
  echo "not used"
fi
```

Write memory: `emotion: upgraded or not-used`

---

## STEP 5  Resolve All Peer Conflicts

```bash
npm ls 2>&1 | grep -E "WARN|ERR|peer|invalid|unmet"
```

For each conflict:

1. Identify the offending package
2. `npm install <package>@latest`
3. Re-check

Rules:

- **Never use `--force`**
- Use `--legacy-peer-deps` only as last resort  document it with a comment in package.json `_notes` field
- If a package has no React 19 compatible release, document it clearly and flag to commander

---

## STEP 6  Clean Install + Final Check

```bash
rm -rf node_modules package-lock.json
npm install
npm ls 2>&1 | grep -E "WARN|ERR|peer" | wc -l
```

**Gate:** Output is `0`.

Write memory: `clean-install: complete, peer-errors: 0`

---

## GO / NO-GO Decision

**GO if:**

- `react@19.x.x` ✅
- `react-dom@19.x.x` ✅
- `@testing-library/react@16.x` ✅
- `npm ls`  0 peer errors ✅

**NO-GO if:** any above fails.

Report GO/NO-GO to commander with exact versions confirmed.
#github-copilot#planningnodejsnpm

Related Skills

More skills in Software Engineering

Accessibility Standards

Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.

#github-copilot#accessibilityMIT

Accord

Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.

#broad-capability#developmentMIT

Acquire Codebase Knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

#github-copilot#documentationMIT

Acreadiness Assess

Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.

#github-copilot#planningMIT

Acreadiness Generate Instructions

Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.

#github-copilot#skillMIT

Acreadiness Policy

Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.

#github-copilot#planningMIT