cc-upgrade

Automate installer-driven upgrades for Claude Cabinet project files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill cc-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-upgrade
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/cc-upgrade
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill cc-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables deterministic, conversational upgrades for Claude Cabinet projects by automating the installer-driven update of upstream files and providing guided explanations of what changed and why.

Core Features & Use Cases

  • Automated upgrade orchestration: runs the installer to deterministically update manifest-tracked skeletons, briefs, and related artifacts, then surfaces a structured explanation of changes.
  • Non-manifest adaptation: guides updates to _briefing.md, phase files, and schema migrations through collaborative reasoning and planning.
  • Change communication: produces human-readable summaries for version bumps, new phase opportunities, and how to adapt the project.

Quick Start

Execute a /cc-upgrade in Claude Code to begin upgrading the Cabinet project to the latest upstream version.

Frequently Asked Questions about cc-upgrade

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

FAQPage Schema
How do I automate schema migrations and skeleton updates for Claude Cabinet projects?

Automated schema migrations and skeleton updates are handled by running the conversational installer, which deterministically updates manifest-tracked files while providing a structured explanation of what changed and why.

What is the process for upgrading phase files and briefing documents in Claude Cabinet?

Upgrading phase files and briefing documents uses collaborative reasoning and planning to guide non-manifest adaptations, ensuring post-upgrade updates are explainable and properly integrated into the project workflow.

How do I get a human-readable summary of changes after a version bump?

Change communication produces human-readable summaries for version bumps by surfacing structured explanations of new phase opportunities and detailing how to adapt the project after the upgrade.

Does the Claude Cabinet upgrade process require manual intervention for non-manifest files?

Non-manifest adaptation requires guided collaborative intervention for files like _briefing.md and phase files, whereas manifest-tracked skeletons and briefs are updated deterministically by the installer without manual input.

How do I start upgrading my Claude Cabinet project to the latest upstream version?

Start upgrading a Claude Cabinet project by executing a /cc-upgrade command in Claude Code, which initiates the installer-driven update process for upstream files and schema migrations.