Finishing a Development Branch
obra/superpowers
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.
Upgrade ostack to the latest version. An agent skill from mr-daedalium/ostack-saas.
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mr-daedalium/ostack-saas ostack-upgrade --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "ostack-upgrade" agent skill from https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgrade into .claude/skills/ostack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ostack-upgrade", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgradeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mr-daedalium/ostack-saas ostack-upgrade --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mr-daedalium/ostack-saas.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ostack-upgrade .agents/skills/ostack-upgrade && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ostack-upgrade" agent skill from https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgrade into .agents/skills/ostack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ostack-upgrade", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mr-daedalium/ostack-saas ostack-upgrade --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mr-daedalium/ostack-saas.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ostack-upgrade .cursor/skills/ostack-upgrade && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ostack-upgrade" agent skill from https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgrade into .cursor/skills/ostack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ostack-upgrade", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mr-daedalium/ostack-saas.git --path ostack-upgrade--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mr-daedalium/ostack-saas ostack-upgrade --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mr-daedalium/ostack-saas.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ostack-upgrade .gemini/skills/ostack-upgrade && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ostack-upgrade" agent skill from https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgrade into .gemini/skills/ostack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ostack-upgrade", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mr-daedalium/ostack-saas ostack-upgradeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mr-daedalium/ostack-saas.git skills-src && mkdir -p .github/skills && cp -r skills-src/ostack-upgrade .github/skills/ostack-upgrade && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ostack-upgrade" agent skill from https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgrade into .github/skills/ostack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ostack-upgrade", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mr-daedalium/ostack-saas --skill ostack-upgrade -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mr-daedalium/ostack-saas ostack-upgrade --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mr-daedalium/ostack-saas.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ostack-upgrade .opencode/skills/ostack-upgrade && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ostack-upgrade" agent skill from https://github.com/mr-daedalium/ostack-saas/tree/main/ostack-upgrade into .opencode/skills/ostack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ostack-upgrade", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ostack-upgradeUpgrade 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. 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.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a67256d. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteAskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Bash, Read, Write, AskUserQuestionAutomated 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.
The full file from mr-daedalium/ostack-saas at commit a67256d, republished under its MIT licence (© mr-daedalium). 634 words, ~2,066 tokens.
.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.<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->
Upgrade ostack to the latest version and show what's new.
This section is referenced by all skill preambles when they detect UPGRADE_AVAILABLE.
First, check if auto-upgrade is enabled:
_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:
If "Yes, upgrade now": Proceed to Step 2.
If "Always keep me up to date":
~/.claude/skills/ostack/bin/ostack-config set auto_upgrade trueTell 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.
_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":
~/.claude/skills/ostack/bin/ostack-config set update_check falseTell user: "Update checks disabled. Run ~/.claude/skills/ostack/bin/ostack-config set update_check true to re-enable."
Continue with the current skill.
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.
Use the install directory from Step 2's output below:
OLD_VERSION=$(cat "$INSTALL_DIR/VERSION" 2>/dev/null || echo "unknown")Use the install type and directory detected in Step 2:
For git installs (global-git, local-git):
cd "$INSTALL_DIR"
STASH_OUTPUT=$(git stash 2>&1)
git fetch origin
git reset --hard origin/main
./setupIf $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):
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"Use the install directory from Step 2. Check if there's also a local vendored copy that needs updating:
_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):
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:
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."
mkdir -p ~/.ostack
echo "$OLD_VERSION" > ~/.ostack/just-upgraded-from
rm -f ~/.ostack/last-update-check
rm -f ~/.ostack/update-snoozedRead $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!After showing What's New, continue with whatever skill the user originally invoked. The upgrade is done — no further action needed.
When invoked directly as /ostack-upgrade (not from a preamble):
~/.claude/skills/ostack/bin/ostack-update-check --force 2>/dev/null || \
.claude/skills/ostack/bin/ostack-update-check --force 2>/dev/null || trueUse the output to determine if an upgrade is available.
If UPGRADE_AVAILABLE <old> <new>: follow Steps 2-6 above.
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:
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
SKILL.md and 1 other file in ostack-upgrade of mr-daedalium/ostack-saas.
Open the folder on GitHubat commit a67256d
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ostack Upgrade this skillmr-daedalium/ostack-saas | 114 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 34 repos | ~1.8k | Automated safety check: Pass | MIT |
obra/superpowers
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.
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.
cursor/plugins
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.
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
farm-fe/farm
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…
TryGhost/Ghost
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.
mr-daedalium/ostack-saas
Fast headless browser for QA testing and site dogfooding. An agent skill from mr-daedalium/ostack-saas.
mr-daedalium/ostack-saas
Performance regression detection using the browse daemon. An agent skill from mr-daedalium/ostack-saas.
mr-daedalium/ostack-saas
Restrict file edits to a specific directory for the session.
mr-daedalium/ostack-saas
Fast headless browser for QA testing and site dogfooding. An agent skill from mr-daedalium/ostack-saas.
mr-daedalium/ostack-saas
Full safety mode: destructive command warnings + directory-scoped edits.
mr-daedalium/ostack-saas
Systematic debugging with root cause investigation. An agent skill from mr-daedalium/ostack-saas.
Works with
Categories
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.
Ostack Upgrade fits situations like: asked to upgrade ostack; get latest version.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.