Agent skill

Ostack Upgrade

by mr-daedalium in mr-daedalium/ostack-saas

Upgrade ostack to the latest version. An agent skill from mr-daedalium/ostack-saas.

MITAuto-check: notesDevelopment

Install Ostack Upgrade

skills CLI
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mr-daedalium/ostack-saas ostack-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mr-daedalium/ostack-saas.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ostack-upgrade .claude/skills/ostack-upgrade && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ostack-upgrade
GitHub stars
114
Token cost
~2.1k tokens
SKILL.md length
634 words
Files
2
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Upgrade ostack to the latest version. An agent skill from mr-daedalium/ostack-saas.

  • Works in 8 steps: Ask the user (or auto-upgrade) → Detect install type → Save old version → …
  • Asked to upgrade ostack
  • SKILL.md covers Inline upgrade flow and Standalone usage
  • Calls git; reaches github.com

What it does

Ostack Upgrade is an agent skill from mr-daedalium/ostack-saas. Upgrade ostack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade ostack", "update ostack", or "get latest version".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in Development. It works with Git. The repository describes itself as: ostack — AI-powered engineering team for Claude Code. Fork of gstack by Garry Tan. The licence is MIT.

When your agent uses it

  • Asked to upgrade ostack
  • Get latest version

Example prompts

  • “s new. Use when asked to”
  • “update ostack”
  • “get latest version”
  • “/ostack-upgrade”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Write, AskUserQuestion

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Ask the user (or auto-upgrade)
  2. Detect install type
  3. Save old version
  4. Upgrade
  5. 5: Sync local vendored copy
  6. Write marker + clear cache
  7. Show What's New
  8. Continue

What it can do on your machine

Read from SKILL.md and the folder at commit a67256d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ostack Upgrade loads about 2.1k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 634 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mr-daedalium/ostack-saas at commit a67256d, republished under its MIT licence (© mr-daedalium). 634 words, ~2,066 tokens.

Download SKILL.mdSave it as .claude/skills/ostack-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ostack-upgrade
description
Upgrade ostack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade ostack", "update ostack", or "get latest version".
allowed-tools
Bash, Read, Write, AskUserQuestion
version
1.1.0
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->

/ostack-upgrade

Upgrade ostack to the latest version and show what's new.

Inline upgrade flow

This section is referenced by all skill preambles when they detect UPGRADE_AVAILABLE.

Step 1: Ask the user (or auto-upgrade)

First, check if auto-upgrade is enabled:

bash
_AUTO=""
[ "${OSTACK_AUTO_UPGRADE:-}" = "1" ] && _AUTO="true"
[ -z "$_AUTO" ] && _AUTO=$(~/.claude/skills/ostack/bin/ostack-config get auto_upgrade 2>/dev/null || true)
echo "AUTO_UPGRADE=$_AUTO"

If AUTO_UPGRADE=true or AUTO_UPGRADE=1: Skip AskUserQuestion. Log "Auto-upgrading ostack v{old} → v{new}..." and proceed directly to Step 2. If ./setup fails during auto-upgrade, restore from backup (.bak directory) and warn the user: "Auto-upgrade failed — restored previous version. Run /ostack-upgrade manually to retry."

Otherwise, use AskUserQuestion:

  • Question: "ostack v{new} is available (you're on v{old}). Upgrade now?"
  • Options: ["Yes, upgrade now", "Always keep me up to date", "Not now", "Never ask again"]

If "Yes, upgrade now": Proceed to Step 2.

If "Always keep me up to date":

bash
~/.claude/skills/ostack/bin/ostack-config set auto_upgrade true

Tell user: "Auto-upgrade enabled. Future updates will install automatically." Then proceed to Step 2.

If "Not now": Write snooze state with escalating backoff (first snooze = 24h, second = 48h, third+ = 1 week), then continue with the current skill. Do not mention the upgrade again.

bash
_SNOOZE_FILE=~/.ostack/update-snoozed
_REMOTE_VER="{new}"
_CUR_LEVEL=0
if [ -f "$_SNOOZE_FILE" ]; then
  _SNOOZED_VER=$(awk '{print $1}' "$_SNOOZE_FILE")
  if [ "$_SNOOZED_VER" = "$_REMOTE_VER" ]; then
    _CUR_LEVEL=$(awk '{print $2}' "$_SNOOZE_FILE")
    case "$_CUR_LEVEL" in *[!0-9]*) _CUR_LEVEL=0 ;; esac
  fi
fi
_NEW_LEVEL=$((_CUR_LEVEL + 1))
[ "$_NEW_LEVEL" -gt 3 ] && _NEW_LEVEL=3
echo "$_REMOTE_VER $_NEW_LEVEL $(date +%s)" > "$_SNOOZE_FILE"

Note: {new} is the remote version from the UPGRADE_AVAILABLE output — substitute it from the update check result.

Tell user the snooze duration: "Next reminder in 24h" (or 48h or 1 week, depending on level). Tip: "Set auto_upgrade: true in ~/.ostack/config.yaml for automatic upgrades."

If "Never ask again":

bash
~/.claude/skills/ostack/bin/ostack-config set update_check false

Tell user: "Update checks disabled. Run ~/.claude/skills/ostack/bin/ostack-config set update_check true to re-enable." Continue with the current skill.

Step 2: Detect install type
bash
if [ -d "$HOME/.claude/skills/ostack/.git" ]; then
  INSTALL_TYPE="global-git"
  INSTALL_DIR="$HOME/.claude/skills/ostack"
elif [ -d "$HOME/.ostack/repos/ostack/.git" ]; then
  INSTALL_TYPE="global-git"
  INSTALL_DIR="$HOME/.ostack/repos/ostack"
elif [ -d ".claude/skills/ostack/.git" ]; then
  INSTALL_TYPE="local-git"
  INSTALL_DIR=".claude/skills/ostack"
elif [ -d ".agents/skills/ostack/.git" ]; then
  INSTALL_TYPE="local-git"
  INSTALL_DIR=".agents/skills/ostack"
elif [ -d ".claude/skills/ostack" ]; then
  INSTALL_TYPE="vendored"
  INSTALL_DIR=".claude/skills/ostack"
elif [ -d "$HOME/.claude/skills/ostack" ]; then
  INSTALL_TYPE="vendored-global"
  INSTALL_DIR="$HOME/.claude/skills/ostack"
else
  echo "ERROR: ostack not found"
  exit 1
fi
echo "Install type: $INSTALL_TYPE at $INSTALL_DIR"

The install type and directory path printed above will be used in all subsequent steps.

Step 3: Save old version

Use the install directory from Step 2's output below:

bash
OLD_VERSION=$(cat "$INSTALL_DIR/VERSION" 2>/dev/null || echo "unknown")
Step 4: Upgrade

Use the install type and directory detected in Step 2:

For git installs (global-git, local-git):

bash
cd "$INSTALL_DIR"
STASH_OUTPUT=$(git stash 2>&1)
git fetch origin
git reset --hard origin/main
./setup

If $STASH_OUTPUT contains "Saved working directory", warn the user: "Note: local changes were stashed. Run git stash pop in the skill directory to restore them."

For vendored installs (vendored, vendored-global):

bash
PARENT=$(dirname "$INSTALL_DIR")
TMP_DIR=$(mktemp -d)
git clone --depth 1 https://github.com/mr-daedalium/ostack.git "$TMP_DIR/ostack"
mv "$INSTALL_DIR" "$INSTALL_DIR.bak"
mv "$TMP_DIR/ostack" "$INSTALL_DIR"
cd "$INSTALL_DIR" && ./setup
rm -rf "$INSTALL_DIR.bak" "$TMP_DIR"
Step 4.5: Sync local vendored copy

Use the install directory from Step 2. Check if there's also a local vendored copy that needs updating:

bash
_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
LOCAL_OSTACK=""
if [ -n "$_ROOT" ] && [ -d "$_ROOT/.claude/skills/ostack" ]; then
  _RESOLVED_LOCAL=$(cd "$_ROOT/.claude/skills/ostack" && pwd -P)
  _RESOLVED_PRIMARY=$(cd "$INSTALL_DIR" && pwd -P)
  if [ "$_RESOLVED_LOCAL" != "$_RESOLVED_PRIMARY" ]; then
    LOCAL_OSTACK="$_ROOT/.claude/skills/ostack"
  fi
fi
echo "LOCAL_OSTACK=$LOCAL_OSTACK"

If LOCAL_OSTACK is non-empty, update it by copying from the freshly-upgraded primary install (same approach as README vendored install):

bash
mv "$LOCAL_OSTACK" "$LOCAL_OSTACK.bak"
cp -Rf "$INSTALL_DIR" "$LOCAL_OSTACK"
rm -rf "$LOCAL_OSTACK/.git"
cd "$LOCAL_OSTACK" && ./setup
rm -rf "$LOCAL_OSTACK.bak"

Tell user: "Also updated vendored copy at $LOCAL_OSTACK — commit .claude/skills/ostack/ when you're ready."

If ./setup fails, restore from backup and warn the user:

bash
rm -rf "$LOCAL_OSTACK"
mv "$LOCAL_OSTACK.bak" "$LOCAL_OSTACK"

Tell user: "Sync failed — restored previous version at $LOCAL_OSTACK. Run /ostack-upgrade manually to retry."

Show full SKILL.md (242 more words)Show less
Step 5: Write marker + clear cache
bash
mkdir -p ~/.ostack
echo "$OLD_VERSION" > ~/.ostack/just-upgraded-from
rm -f ~/.ostack/last-update-check
rm -f ~/.ostack/update-snoozed
Step 6: Show What's New

Read $INSTALL_DIR/CHANGELOG.md. Find all version entries between the old version and the new version. Summarize as 5-7 bullets grouped by theme. Don't overwhelm — focus on user-facing changes. Skip internal refactors unless they're significant.

Format:

ostack v{new} — upgraded from v{old}!

What's new:
- [bullet 1]
- [bullet 2]
- ...

Happy shipping!
Step 7: Continue

After showing What's New, continue with whatever skill the user originally invoked. The upgrade is done — no further action needed.


Standalone usage

When invoked directly as /ostack-upgrade (not from a preamble):

  1. Force a fresh update check (bypass cache):
bash
~/.claude/skills/ostack/bin/ostack-update-check --force 2>/dev/null || \
.claude/skills/ostack/bin/ostack-update-check --force 2>/dev/null || true

Use the output to determine if an upgrade is available.

  1. If UPGRADE_AVAILABLE <old> <new>: follow Steps 2-6 above.

  2. If no output (primary is up to date): check for a stale local vendored copy.

Run the Step 2 bash block above to detect the primary install type and directory (INSTALL_TYPE and INSTALL_DIR). Then run the Step 4.5 detection bash block above to check for a local vendored copy (LOCAL_OSTACK).

If LOCAL_OSTACK is empty (no local vendored copy): tell the user "You're already on the latest version (v{version})."

If LOCAL_OSTACK is non-empty, compare versions:

bash
PRIMARY_VER=$(cat "$INSTALL_DIR/VERSION" 2>/dev/null || echo "unknown")
LOCAL_VER=$(cat "$LOCAL_OSTACK/VERSION" 2>/dev/null || echo "unknown")
echo "PRIMARY=$PRIMARY_VER LOCAL=$LOCAL_VER"

If versions differ: follow the Step 4.5 sync bash block above to update the local copy from the primary. Tell user: "Global v{PRIMARY_VER} is up to date. Updated local vendored copy from v{LOCAL_VER} → v{PRIMARY_VER}. Commit .claude/skills/ostack/ when you're ready."

If versions match: tell the user "You're on the latest version (v{PRIMARY_VER}). Global and local vendored copy are both up to date."

© mr-daedalium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in ostack-upgrade of mr-daedalium/ostack-saas.

  • SKILL.md
  • SKILL.md.tmpl

Open the folder on GitHubat commit a67256d

Compare with similar skills

Ostack Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ostack Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ostack Upgrade this skillmr-daedalium/ostack-saas114—~2.1kAutomated safety check: NotesMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins11k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    11k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

More from mr-daedalium/ostack-saas

All 23 skills in this repo
  • Browse

    mr-daedalium/ostack-saas

    Fast headless browser for QA testing and site dogfooding. An agent skill from mr-daedalium/ostack-saas.

    114 GitHub starsUsed in 1 repo~5.3k tokens
    Auto-check: notes
  • Benchmark

    mr-daedalium/ostack-saas

    Performance regression detection using the browse daemon. An agent skill from mr-daedalium/ostack-saas.

    114 GitHub starsUsed in 1 repo~5k tokens
    Auto-check: notes
  • Freeze

    mr-daedalium/ostack-saas

    Restrict file edits to a specific directory for the session.

    114 GitHub starsUsed in 1 repo~681 tokens
    Auto-check: notes
  • Ostack

    mr-daedalium/ostack-saas

    Fast headless browser for QA testing and site dogfooding. An agent skill from mr-daedalium/ostack-saas.

    114 GitHub stars~6.1k tokensUpdated 6 mo ago
    Auto-check: notes
  • Guard

    mr-daedalium/ostack-saas

    Full safety mode: destructive command warnings + directory-scoped edits.

    114 GitHub starsUsed in 1 repo~720 tokens
    Auto-check: notes
  • Investigate

    mr-daedalium/ostack-saas

    Systematic debugging with root cause investigation. An agent skill from mr-daedalium/ostack-saas.

    114 GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check: notes

Works with

Categories

Questions about Ostack Upgrade

What does Ostack Upgrade do?

Upgrade ostack to the latest version. An agent skill from mr-daedalium/ostack-saas. Ostack Upgrade is an agent skill from mr-daedalium/ostack-saas. Upgrade ostack to the latest version.

When should I use Ostack Upgrade?

Ostack Upgrade fits situations like: asked to upgrade ostack; get latest version.

How do I install Ostack Upgrade in Claude Code?

Run `npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a claude-code`. Or copy the skill folder (ostack-upgrade in mr-daedalium/ostack-saas) into .claude/skills/ostack-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Ostack Upgrade in Codex?

Run `npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a codex`. Or copy the skill folder (ostack-upgrade in mr-daedalium/ostack-saas) into .agents/skills/ostack-upgrade in your project. Codex loads it when a task matches its description.

Can I use Ostack Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ostack-upgrade, .gemini/skills/ostack-upgrade, .github/skills/ostack-upgrade and .opencode/skills/ostack-upgrade in your project.

What does Ostack Upgrade need to run?

Going by SKILL.md and its folder, Ostack Upgrade needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash, Read, Write, AskUserQuestion.

Does Ostack Upgrade access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Ostack Upgrade safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ostack Upgrade use?

Ostack Upgrade is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ostack Upgrade use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ostack Upgrade?

Skills that share tags, products or a category with Ostack Upgrade: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ostack Upgrade?

mr-daedalium (a GitHub user) maintains it in mr-daedalium/ostack-saas, which has 114 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on March 31, 2026.

Source: mr-daedalium/ostack-saas on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.