Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Search & research

ln-32-dependency-upgrader

Upgrades dependencies across package managers with breaking-change research and rollback-safe verification. Use for dependency maintenance; not general code modernization.

levnikolaevich · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add levnikolaevich/claude-code-skills --skill ln-32-dependency-upgrader

About this skill


name: ln-32-dependency-upgrader description: "Upgrades dependencies across package managers with breaking-change research and rollback-safe verification. Use for dependency maintenance; not general code modernization."

Dependency Upgrader

Goal: Upgrade dependencies in small, attributable batches. Preserve manifests, lockfiles, runtime support, and product behavior; do not treat a newer version as valuable without compatibility, security, or maintenance evidence.

Execution contract: Treat the ordered checkbox workflow below as this skill's Definition of Done. Track every checkbox as PENDING, then resolve it to PROVEN with concrete evidence, CLEARED with evidence that its conditional trigger is absent, or UNPROVEN; reading, mentioning, delegating, skipping, or tool failure is not proof. Before returning, resolve every PENDING, count only PROVEN and CLEARED items as complete, apply this skill's verdict, decision, and approval rules to every UNPROVEN, and prepend Checklist: X/Y completeIncomplete: None | section/item — reason; outcome impact; exact next action; list every UNPROVEN item.

Tool Routing

NeedPreferred toolUse it whenFallback
Package-manager detectionManifests, lockfiles, workspace files, runtime files, and repository instructionsAlways before choosing commands or update scopeBuild and CI configuration
Outdated and vulnerable packagesNative package-manager outdated and audit commandsThe manager and registry are availableOfficial registry, vendor advisory, and lockfile inspection
Breaking changes and supportOfficial release notes, migration guides, changelogs, advisories, and runtime support tablesEvery consequential minor, major, replacement, or security updatePrimary-source repository releases; otherwise mark UNVERIFIED
Usage and blast radiusLanguage server or host-native code intelligenceAn updated API, type, plugin, build tool, or runtime may affect consumersTargeted import, symbol, configuration, and script search
Safe version changesNative package-manager commandsUpdating manifests and generated lock stateDo not hand-edit lockfiles or emulate package resolution
VerificationRepository-defined install, restore, build, lint, type, test, migration, and smoke commandsBefore changes and after each batchCI and script inspection with explicit unverified status
Diff and rollbackGit status, diff, and isolated commits or worktreeProtecting user changes and reverting only the failed batchStop if the batch cannot be isolated safely

Never publish packages, rotate credentials, deploy, or weaken audit and verification gates. Do not run lifecycle scripts from an untrusted package source without the environment's normal safeguards.

Evidence Rules

  • Manifests and lockfiles define what is installed; registry "latest" does not override project runtime or compatibility constraints.
  • A vulnerability finding requires the affected version, advisory, reachability or exposure context, and a credible remediation.
  • A breaking-change claim requires release or migration evidence matching the exact version transition.
  • Keep generated lockfile changes only when produced by the selected native package manager and expected repository version.
  • Upgrade success requires repository verification, not only a successful install or restore.

Checklist

1. Discover Scope and Protect the Workspace

  • Detect all package managers, workspaces, manifests, lockfiles, central version files, registries, runtime pins, tool manifests, and generated dependency files.
  • Classify each deliverable as an application, library, plugin, CLI, container, or build tool so version ranges, lockfiles, peer constraints, and supported-runtime promises are interpreted correctly.
  • Read repository instructions and determine supported package-manager versions, update commands, lockfile policy, and CI expectations.
  • Inspect Git state and isolate the work so existing user changes cannot be overwritten or mistaken for upgrade output.
  • Start a run-owned resource ledger with every created absolute path, worktree, process ID, cache, report, and temporary artifact; never register pre-existing resources as cleanup targets.
  • Resolve the requested scope: security-only, routine patch or minor maintenance, selected packages, majors, runtime migration, or complete refresh.
  • Capture install or restore, build, lint, type, test, smoke, and security-audit baseline before editing.
  • Record pre-existing failures, advisories, deprecations, peer conflicts, and unsupported runtime combinations.

2. Research and Plan Batches

  • Use native outdated and audit commands to inventory direct and relevant transitive updates without changing files.
  • Separate removals, security fixes, routine updates, major changes, build-tool changes, and runtime or ecosystem migrations.
  • Check official release notes and migration guides for API changes, configuration changes, defaults, peer constraints, runtime support, and removed behavior.
  • Resolve environment markers, extras, optional/dev groups, peer dependencies, target frameworks, and platform-specific packages; a graph that resolves only on the current machine is not sufficient when the project promises a wider matrix.
  • Check official advisories for affected ranges, exploit conditions, fixed versions, workarounds, and whether the dependency is reachable in this project.
  • Search actual imports, symbols, plugins, scripts, configuration, generated code, and runtime loading for every consequential dependency.
  • Identify unused, duplicate, abandoned, replaced, or platform-redundant dependencies as separate removal candidates; require runtime and dynamic-loading evidence, and explicit user approval when removal is outside the requested upgrade scope.
  • Order batches by pre
Read the complete source ↗