Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
Dependency Upgrade
Manage major dependency version upgrades with compatibility analysis, staged rollout, and…
A disciplined approach to major dependency and framework upgrades: compatibility analysis, staged rollout, breaking-change handling, and comprehensive testing. It upgrades one dependency at a time to keep the blast radius small, reads changelogs for breaking changes, applies codemods for automated fixes, and keeps a rollback plan ready at every step.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
The skill never runs a blanket update. It executes a staged, one-package-at-a-time upgrade loop with a rollback path prepared before anything moves:
- Audit first: npm outdated, npm audit and npx npm-check-updates list what is behind and what carries CVEs. npm ls and madge map who depends on what, so the blast radius of each bump is known up front.
- Read the changelogs and migration guides for every MAJOR jump, then write an explicit upgrade order (for example: TypeScript, then React, then Router, then testing libraries, then build tools). Skipping major versions is banned, 16 to 17 to 18, never 16 to 18.
- Baseline: full test suite on a feature branch with a git tag backup before the first install.
- Upgrade ONE dependency, run the entire test suite plus build, check bundle size impact, resolve peer dependency warnings, then move to the next. A failure is isolated to exactly one step instead of twenty.
- Where available, codemods automate the breaking-change mechanics (lifecycle renames, import rewrites); a compatibility test asserts paired versions match (react equals react-dom).
- If tests fail and cannot be fixed, the rollback script restores from the lock file and deletes the branch. Minor and patch updates get automated afterwards via Renovate or Dependabot with automerge rules, majors stay manual.
One power source. 6 lines out.
dependency-upgrade · core
core active · 6 lines
- ✓ upgrading a major framew…
Upgrading a major framework version like a UI library or router
- ✓ patching security-vulner…
Patching security-vulnerable dependencies flagged by an audit
- ✓ resolving peer dependency
Resolving peer dependency conflicts and duplicate packages
- ✓ planning an incremental
Planning an incremental upgrade path across multiple major versions
- ✓ setting up automated upd…
Setting up automated update bots with safe automerge rules
- ✓ running a tested rollback
Running a tested rollback when an upgrade fails its test suite
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Avoid the chaos of all-at-once upgrades by isolating each change for easy debugging
license: perpetual -
Catch breaking changes before they ship by reading changelogs and applying codemods
license: perpetual -
Keep upgrades reversible with a baseline test run, lock files, and a scripted rollback
license: perpetual -
Stay current and secure with automated update bots tuned for safe versus major changes
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
A semantic-versioning and semver-range strategy (caret, tilde, exact) per dependency type
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Developers and tech leads managing major dependency or framework upgrades on a production codebase.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
I have a long list of outdated packages. Does the one-at-a-time rule mean this drags on forever?
One dependency at a time is deliberate: it keeps the blast radius small so a break is easy to trace to a single change. It is slower than a bulk bump, but it trades a few extra passes for upgrades that do not leave you bisecting a tangle of failures.
-
Codemods automate the easy changes. What happens to breaking changes a codemod can't cover?
Codemods handle the mechanical rewrites, and the guide reads changelogs to surface the rest so you address them by hand. The point is to separate what can be automated from what needs judgment, not to pretend every break is scriptable.
-
Does this guarantee nothing breaks after an upgrade?
It cuts the risk through staged rollout, compatibility analysis, and testing, but it leans on the test coverage you already have. Where your tests are thin, a breaking change can still slip past, so the safety is real but not absolute.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.