featureforge-upgrade

Upgrade the local FeatureForge runtime by stashing changes and pulling updates.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/dmulcahey/featureforge --skill featureforge-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: featureforge-upgrade
Source: https://github.com/dmulcahey/featureforge/tree/main/featureforge-upgrade
Command: npx skills add https://github.com/dmulcahey/featureforge --skill featureforge-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates upgrading the local FeatureForge runtime when a newer version is detected, ensuring teams stay on supported releases without manual steps and providing a clear summary of changes.

Core Features & Use Cases

  • Automatically detect upgrade eligibility and advise on next steps.
  • Resolve the active install root and perform a safe, auditable upgrade by stashing local changes, pulling updates, and recording the new version.
  • Provide a summary of what's changed by reading RELEASE-NOTES.md and updating upgrade state for traceability.
  • Handle auto-upgrade preferences and interactive prompts to fit workflow needs and reduce downtime in CI or developer machines.

Quick Start

Invoke this skill to upgrade the local FeatureForge runtime to the latest version.

Frequently Asked Questions about featureforge-upgrade

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

FAQPage Schema
How do I upgrade my local runtime to the latest version using git?

Upgrading your local runtime involves stashing local changes via git, pulling updates from the repository, and recording the new version to ensure a safe, auditable upgrade across your local install.

Can I automate versioning upgrades for my development environment?

Yes, you can automate versioning upgrades by handling auto-upgrade preferences and interactive prompts, reducing downtime in CI pipelines or developer machines without manual intervention.

Does the upgrade workflow require access to a specific install path?

Yes, the upgrade workflow requires access to the local install path, the runtime binary, and git to successfully stash changes and pull updates during the versioning process.

What is the best way to summarize changes after a version upgrade?

Summarizing changes after a version upgrade is handled by reading RELEASE-NOTES.md and updating the upgrade state, providing a clear summary of what has changed for traceability.

How does the upgrade process handle local changes before pulling updates?

The upgrade process handles local changes by using git to stash them before pulling updates, ensuring that local modifications are safely preserved during the runtime upgrade.