agent-upgrade

Migrates Claude Agent project configs from older schema versions to the current schema with backups.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill agent-upgrade-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-upgrade
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/agent-upgrade
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill agent-upgrade-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects initialized on older versions of the Claude Agent framework accumulate outdated config layouts (inline testing/build blocks, root-level mac_build, missing workflow.backend). This Skill upgrades those projects to the current schema without losing data or making silent destructive changes. ## Core Features & Use Cases - Schema version detection: Classifies a project as v1, v2, or v3 by inspecting the root agent.yaml, then runs only the migration steps needed. - Interactive, non-destructive migration: Builds a full migration ledger, asks the user to resolve every conflict and fastlane suggestion, backs up all affected files to .workflow/upgrade-backup-<timestamp>/ before writing anything. - Multi-shape support: Handles single-repo, multi-repo, and mono-repo expansions, moving per-repo config into agent-build.yaml leaf files and migrating iOS mac_build settings. - Use Case: A team whose project was initialized on schema v1 runs the upgrade; the Skill extracts inline testing/build commands into per-repo agent-build.yaml files, rewrites the root agent.yaml to the pointer shape, validates task file Repo: references, and leaves a restorable backup. ## Quick Start Ask the agent to upgrade this project's agent config to the current schema and confirm each proposed change before it is written.

Frequently Asked Questions about agent-upgrade

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

FAQPage Schema
How do I upgrade an agent.yaml project to the latest config schema?▼

Run the agent-upgrade skill in the project root. It detects the current schema version from agent.yaml, builds a migration ledger of every planned change, and applies the v1-to-v2 and v2-to-v3 steps only after you confirm.

How does the skill detect which schema version a project uses?▼

It reads the root agent.yaml. Presence of workflow.backend means v3; repos with build pointers to agent-build.yaml but no backend key means v2; inline testing/build blocks or a root mac_build block means v1.

Is the agent config migration destructive or reversible?▼

It is non-destructive by default. Every modified or deleted file is first copied into .workflow/upgrade-backup-<timestamp>/ with its original path preserved, plus a MANIFEST.md with sizes and sha256 hashes, so state can be restored.

What happens when root and per-repo agent.yaml values conflict?▼

The migration pauses and asks you to pick which value to keep, offering both values plus a free-form Other option. It never guesses or silently overwrites divergent testing or build commands.

Can the migration handle mono-repos and iOS mac_build settings?▼

Yes. It detects directories containing multiple sub-projects and offers to expand them into a mono-repo parent with per-sub-project agent-build.yaml files. Root-level mac_build host and workspace values move into each iOS leaf config.

What changes in the v2 to v3 upgrade step?▼

The v3 migration adds an explicit workflow.backend key. Choosing markdown inserts one line with no behavioral change; choosing github_project delegates to the agent-migrate skill, which provisions a GitHub Project board and updates agent.yaml itself.