code-upgrade

Identify upgrade types and target versions for project dependencies and frameworks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sirn/dotfiles --skill code-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-upgrade
Source: https://github.com/sirn/dotfiles/tree/main/var/agents/skills/code-upgrade
Command: npx skills add https://github.com/sirn/dotfiles --skill code-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely upgrade dependencies or migrate framework versions across projects to reduce risk and maintain compatibility.

Core Features & Use Cases

  • Identify upgrade type: single dependency, all dependencies, framework migration, or language runtime upgrade.
  • Analyze current state and collect current versions from dependency files (e.g., package.json, pyproject.toml, etc.).
  • Generate a migration plan with deprecations, breaking changes, and testing steps.

Quick Start

Upgrade the project's dependencies to the desired versions.

Frequently Asked Questions about code-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely upgrade dependencies and migrate framework versions in my codebase?

To safely upgrade dependencies and migrate framework versions, the Skill analyzes your current state, identifies the upgrade type, researches breaking changes, and generates a detailed migration plan before executing any updates.

What is the process for planning a framework migration across different package managers?

Planning a framework migration involves collecting current versions from dependency files like package.json or pyproject.toml, identifying target versions, and presenting deprecations and testing steps to ensure compatibility.

Can I upgrade all project dependencies at once or should I upgrade them individually?

You can do both. The Skill identifies whether you need a single dependency upgrade, an all-dependency upgrade, a framework migration, or a language-runtime upgrade, and adapts its analysis and planning accordingly.

What's the best way to handle breaking changes when upgrading a language runtime?

The best way to handle breaking changes during a language runtime upgrade is to analyze the current codebase state, research the specific runtime changes, and generate a step-by-step migration plan with required testing.

Does this dependency upgrade approach work with diverse programming languages and package managers?

Yes, this dependency upgrade approach applies to codebases with diverse package managers and languages by analyzing current versions from various dependency files to formulate a safe, comprehensive migration plan.