skills.rest
reliant-labs
reliant-labsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

upgrade

Upgrade forge projects to a target binary version with migration skills.

4|1|Updated Apr 12, 2026
Search Tags:#rollback#verification#migration#version pinning#forge#cli upgrade#template drift
One-click install
npx skills add https://github.com/reliant-labs/forge --skill upgrade-reliant-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/migration/upgrade
Command: npx skills add https://github.com/reliant-labs/forge --skill upgrade-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading an existing forge-generated project can be risky when the forge binary on your PATH no longer matches the version pinned in forge.yaml, especially when generated artifacts evolve across releases.

Core Features & Use Cases

  • Version-aware migration orchestration: Detects the correct per-version migration skills by matching the project’s pinned forge_version family to the available migration registry.
  • Deterministic upgrade steps: Runs the automation phase for regeneration/build steps that are safe to compute, then surfaces the remaining manual changes for user-edited code.
  • Template drift handling and verification guidance: Diffs frozen Tier-2 files against latest templates to show unified diffs for modified files, updates unmodified ones, bumps forge_version in forge.yaml, and describes verification and rollback expectations.

Quick Start

Tell the AI: “Inspect forge.yaml and my current forge version, then guide me through running forge upgrade (including any dry-run), loading any surfaced migration skills, applying the manual steps, and verifying the result with build and tests.”

Frequently Asked Questions about upgrade

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

FAQPage Schema
How do I safely upgrade a forge project when my forge binary version doesn't match forge.yaml?▼

Forge upgrade resolves version mismatches between the pinned forge_version in forge.yaml and the installed forge binary by discovering applicable migration skills, applying deterministic regeneration, and updating the pin after manual changes.

How does template drift handling work when upgrading forge generated files?▼

Template drift handling during a forge upgrade diffs frozen Tier-2 files against latest templates to display unified diffs for modified files, updates unmodified ones automatically, and bumps the forge_version in forge.yaml.

What is the process to migrate forge projects across different binary versions?▼

Migrating forge projects involves walking skills/forge/migration/v*-to-* directories to match the from prefix to the project's forge_version family, applying automated regeneration steps, and completing required manual portions before updating the version pin.

How do I prepare for verification and rollback when upgrading my forge version?▼

Verification and rollback planning for a forge upgrade requires running build and tests after applying automated and manual migration steps, then following the provided rollback guidance to safely revert the forge_version pin if verification fails.

Can I run a dry-run before applying a forge upgrade to my project?▼

Yes, you can execute a dry-run to preview the forge upgrade process, review template drift diffs, and load applicable migration skills before applying automated regeneration or updating the forge_version in forge.yaml.

Why does forge generate warn about a version mismatch with my project?▼

Forge generate warns about a version mismatch because the installed forge binary is newer than the forge_version pinned in forge.yaml, indicating generated artifacts may have evolved and require a structured upgrade to resolve.

Related Skills

Explore More Software Engineering Skills→
reliant-labsreliant-labs
4

v0.x-to-env-config

Migrates forge projects from KCL env-var groups to forge.yaml per-environment config.

Official
Intermediate
pontschopontscho
1

p:forge

Route build, test, and clean commands through forge_call when project-forge.yaml exists.

Community
Intermediate
garethrhughesgarethrhughes
5

upgrade-rules-v2

Migrate CLAUDE.md from rules v1 to v2 with stack detection.

Community
Advanced
yesplease-studioyesplease-studio
2

prd-context-pack

Compile frozen PRD and ADR contracts into a validated CONTEXT-PACK.md.

Official
Advanced