Skill Details
Runtime
(claude-5-5-opus)
Example user message
[userMessage]: Dependabot grouped 6 updates into one PR (git diff is in deps.diff). I pasted the @corp/forms 2.0 migration notes into forms-2.md. What can I merge right now?
Example agent response
DEPENDENCY UPGRADE RISK REVIEW
Evidence: package.json diff, 41 source files, release notes for @corp/forms; no lockfile.
Verdict: 6 changes: 1 HIGH, 1 MEDIUM, 4 LOW/INFO. Merge 4 now, check 1, fix 1 first.
MERGE PLAN
1. Merge now: dayjs 1.11.10 to 1.11.13, eslint 8.56 to 8.57, vitest-mock-extended (range only), yargs 16 to 17 (major, but no import found)
2. Check first: @tanstack/virtual-core 0.9 to 0.10. This is a 0.x minor, so semver allows breaking changes. Used in src/table/VirtualRows.tsx. Read its changelog for useVirtualizer options.
3. Fix before merging: @corp/forms 1.8 to 2.0
@corp/forms, BREAKING-USED, HIGH (confidence HIGH)
Change: validateOn renamed to mode (source: supplied notes)
Used at: src/checkout/AddressForm.tsx:22, src/account/ProfileForm.tsx:31
Not affected: SearchBar.tsx:9 also passes validateOn, but to a local component, not @corp/forms.
Action: rename validateOn to mode at the 2 call sites.
Instant access
Commercial use
Money‑backBy purchasing this skill, you agree to our terms of service
CLAUDE-5-5-OPUS
Dependabot or Renovate PR? Find what will actually break before you merge. This Claude Code skill compares package upgrades with your real Node/TypeScript code, flags breaking changes that affect APIs you actually use, ignores irrelevant major bumps and look-alike names, and gives you a clear plan: MERGE NOW, CHECK FIRST, or FIX BEFORE MERGING—with exact files and confidence for each risk.
...more
Added 52 minutes ago
