update-orc

Updates an installed orc pack to the latest GitHub release using cumulative changelog migration maps.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/rogadev/orc-pack --skill update-orc-rogadev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-orc
Source: https://github.com/rogadev/orc-pack/tree/main/skills/update-orc
Command: npx skills add https://github.com/rogadev/orc-pack --skill update-orc-rogadev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a copied-into-.claude/ orc pack installation current is error-prone when the install is several releases behind, since renames, removals, and migration steps accumulate across versions. This Skill automates the full upgrade path in one pass, converging the install on the latest released kit without manual diffing. ## Core Features & Use Cases - Version and provenance detection: Reads the local pack version marker and provenance file to establish the installed version, source repo, and install root. - Cumulative migration map: Fetches the latest GitHub release via gh, assembles every in-range changelog section into an ordered update map, and falls back to a git diff when release notes are thin. - Subagent-driven convergence: Dispatches the orc-updater subagent (Opus 4.8) to converge the install on the fetched kit, then verifies file parity, frontmatter integrity, and provenance re-recording. - Use Case: You installed orc-pack 1.1.0 months ago and the latest release is 1.4.0. Run the update and the Skill applies all intermediate migrations, refreshes every pack file, preserves your local edits, and reports the full transition. ## Quick Start Ask the assistant to update the orc pack to the latest release and it will detect your installed version, fetch the newest kit, and converge the installation.

Frequently Asked Questions about update-orc

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

FAQPage Schema
How do I update the orc pack to the latest version?

Run the update-orc skill in the repo where the pack is installed. It reads your installed version from the pack marker and provenance file, fetches the latest GitHub release, builds a migration map from all in-range changelog entries, and converges the install on the new kit.

Can I update orc-pack when several releases behind?

Yes, the skill handles multi-release jumps in one pass. It assembles every changelog section between your installed version and the target into a cumulative migration map, so renames, removals, and migration steps across the whole gap are applied.

Does updating orc-pack overwrite my local edits?

No, documented local edits recorded in provenance are preserved and re-applied after convergence. Files without a pack: marker are treated as repo-owned and are never clobbered by the updater.

What happens if the changelog has no migration steps?

The skill falls back to a git diff between the installed and target versions, or compares installed files against the fetched kit directly when tags are missing. The update proceeds with the diff labeled as a fallback map in the report.

Why does the orc pack update fail with a gh error?

The update requires the GitHub CLI (gh) to be installed and authenticated to fetch releases and clone the target tag. If gh is missing or unauthenticated, the skill stops and reports UPDATE FAILED with that blocker.