skills.rest
mr-daedalium
mr-daedaliumCOMMUNITY
Explore all skills by this author →
Website𝕏@daedaliumGitHub

ostack-upgrade

Detect ostack install type, upgrade to latest version, and sync vendored copies.

107|19|Updated Mar 23, 2026
Search Tags:#automation#upgrade#version-control#change-log#vendored#ostack
One-click install
npx skills add https://github.com/mr-daedalium/ostack --skill ostack-upgrade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ostack-upgrade
Source: https://github.com/mr-daedalium/ostack/tree/main/ostack-upgrade
Command: npx skills add https://github.com/mr-daedalium/ostack --skill ostack-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates upgrading ostack to the latest version, handling both global and vendored installs and surfacing what's new.

Core Features & Use Cases

  • Detects install type (global, local, vendored) and performs the upgrade steps.
  • Syncs local vendored copies after upgrade to keep all copies aligned.
  • Showcases what's new by parsing CHANGELOG.md and highlighting user-facing changes.

Quick Start

Run the /ostack-upgrade command to upgrade your installed ostack to the latest version.

Frequently Asked Questions about ostack-upgrade

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

FAQPage Schema
How do I upgrade ostack to the latest version across different installation types?▼

To upgrade ostack, the Skill automatically detects your installation type—global, local, or vendored—and performs the appropriate upgrade steps to ensure you are running the latest version.

Can I sync vendored copies after upgrading ostack?▼

Yes, the ostack upgrade process automatically syncs local vendored copies after the main upgrade completes, keeping all aligned with the newly installed latest version.

What is the best way to see what changed in the latest ostack upgrade?▼

The best way to see what changed is using this automated upgrade Skill, which parses the CHANGELOG.md file and highlights user-facing changes immediately after the version update completes.

Does the ostack upgrade workflow work with both global and local installations?▼

Yes, the ostack upgrade workflow supports global, local, and vendored installations by detecting the install type during execution and applying the correct upgrade steps for that specific environment.

Why do I need to detect install type before upgrading ostack?▼

Detecting the install type is required before upgrading ostack because global, local, and vendored installations each require different upgrade steps and synchronization methods to successfully propagate version changes.

How do I automate version control updates for a vendored ostack installation?▼

You can automate vendored ostack updates by running the upgrade command, which detects the vendored install type, upgrades the base package, and automatically syncs the changes to all local vendored copies.

Related Skills

Explore More Software Engineering Skills→
PacificStudioPacificStudio
264

install-codex

Install or upgrade Codex CLI and verify codex --version.

Official
Intermediate
fghaffarfghaffar

gstack-upgrade

Upgrade gstack installations and summarize user-facing changelog changes.

Community
Advanced
rioX432rioX432
11

release

Automate version bumps, changelog updates, git tagging, and code pushes.

Community
Intermediate
harsh-m-patilharsh-m-patil

next-upgrade

Upgrade Next.js projects to the latest version using official migration guides and codemods.

Community
Advanced