skills.rest
eveld
eveldCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

upgrade-plugin

Migrate projects by executing CHANGELOG.md version-specific steps.

10|2|Updated Dec 23, 2025
Search Tags:#automation#changelog#versioning#migrations#plugin#project-upgrade
One-click install
npx skills add https://github.com/eveld/claude --skill upgrade-plugin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade-plugin
Source: https://github.com/eveld/claude/tree/main/skills/upgrade-plugin
Command: npx skills add https://github.com/eveld/claude --skill upgrade-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates project-level migrations by treating the CHANGELOG.md as the single source of truth for version-specific steps, reducing drift and manual reconciliation.

Core Features & Use Cases

  • Reads the current project version from thoughts/.version and determines the target version from CHANGELOG.md.
  • Executes migration steps in defined order, prompts for decisions via a built-in questions system, and preserves originals until confirmation.
  • Updates thoughts/.version after successful migrations and generates a migration report.

Quick Start

Run the upgrade workflow to migrate your project using CHANGELOG-driven steps.

Frequently Asked Questions about upgrade-plugin

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

FAQPage Schema
How do I automate project migrations using a changelog?▼

Automate project migrations by reading CHANGELOG.md to drive version-specific steps. The system executes migration steps in defined order, prompts for decisions, and preserves originals until confirmation. It treats the changelog as the single source of truth to reduce drift and manual reconciliation.

What files do I need to set up before running a changelog-driven migration?▼

Changelog-driven migrations require a CHANGELOG.md in the plugin directory and a thoughts/.version file. The version file determines the current project version, while the changelog defines the target version and the specific migration steps required between them.

How does incremental version migration work with planned migration sections?▼

Incremental version migration works by reading the current version from thoughts/.version and the target from CHANGELOG.md. It executes planned migration sections in defined order, prompts for user decisions along the way, and updates the version file only after a successful migration.

Can I preserve original files until a migration is confirmed?▼

Yes, the migration process preserves originals until confirmation. It executes changelog-driven steps, uses a built-in questions system to prompt for decisions, and only updates the thoughts/.version file and generates a final migration report after successful completion.

What is the best way to coordinate version-specific steps across multiple projects?▼

Coordinate version-specific steps by treating CHANGELOG.md as the single source of truth. The system operates within each project's thoughts/ directory, reads version files, executes ordered migrations, prompts for decisions, and generates reports to reduce manual reconciliation across projects.

Related Skills

Explore More Software Engineering Skills→
auth0auth0
40

auth0-android-major-migration

Upgrade Auth0 Android SDK integrations to the next major version.

Official
Advanced
metaloozeemetaloozee
2

next-upgrade

Detect the current Next.js version, run official codemods, and update dependencies.

Community
Intermediate
poncardasmponcardasm

changelog-manager

Create and update CHANGELOG.md files using Keep a Changelog and Semantic Versioning.

Community
Intermediate
tobihagemanntobihagemann
399

update-deps

Upgrade project dependencies across multiple package managers with breaking change research.

Community
Advanced