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 pstack to the latest version. An agent skill from no-session/pstack.
$ npx skills add no-session/pstack --skill pstack-upgrade -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install no-session/pstack pstack-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/no-session/pstack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pstack-upgrade .claude/skills/pstack-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 "pstack-upgrade" agent skill from https://github.com/no-session/pstack/tree/main/pstack-upgrade into .claude/skills/pstack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pstack-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/no-session/pstack/tree/main/pstack-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 no-session/pstack --skill pstack-upgrade -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install no-session/pstack pstack-upgrade --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-session/pstack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pstack-upgrade .agents/skills/pstack-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 "pstack-upgrade" agent skill from https://github.com/no-session/pstack/tree/main/pstack-upgrade into .agents/skills/pstack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pstack-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 no-session/pstack --skill pstack-upgrade -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install no-session/pstack pstack-upgrade --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-session/pstack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pstack-upgrade .cursor/skills/pstack-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 "pstack-upgrade" agent skill from https://github.com/no-session/pstack/tree/main/pstack-upgrade into .cursor/skills/pstack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pstack-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/no-session/pstack.git --path pstack-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 no-session/pstack --skill pstack-upgrade -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install no-session/pstack pstack-upgrade --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-session/pstack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pstack-upgrade .gemini/skills/pstack-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 "pstack-upgrade" agent skill from https://github.com/no-session/pstack/tree/main/pstack-upgrade into .gemini/skills/pstack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pstack-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 no-session/pstack pstack-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 no-session/pstack --skill pstack-upgrade -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/no-session/pstack.git skills-src && mkdir -p .github/skills && cp -r skills-src/pstack-upgrade .github/skills/pstack-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 "pstack-upgrade" agent skill from https://github.com/no-session/pstack/tree/main/pstack-upgrade into .github/skills/pstack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pstack-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 no-session/pstack --skill pstack-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 no-session/pstack pstack-upgrade --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-session/pstack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pstack-upgrade .opencode/skills/pstack-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 "pstack-upgrade" agent skill from https://github.com/no-session/pstack/tree/main/pstack-upgrade into .opencode/skills/pstack-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pstack-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.
pstack-upgradeUpgrade pstack to the latest version. An agent skill from no-session/pstack.
Pstack Upgrade is an agent skill from no-session/pstack. Upgrade pstack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade pstack", "update pstack", 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: The solo founder's AI engineering stack. Fork of gstack, rebuilt for bootstrappers, indie hackers, and people who want to quit their day job. Pieter Levels energy. Ship fast… The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9a24d14. 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.
Pstack 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 no-session/pstack at commit 9a24d14, republished under its MIT licence (© no-session). 634 words, ~2,065 tokens.
.claude/skills/pstack-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 pstack 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=""
[ "${PSTACK_AUTO_UPGRADE:-}" = "1" ] && _AUTO="true"
[ -z "$_AUTO" ] && _AUTO=$(~/.claude/skills/pstack/bin/pstack-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 pstack 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 /pstack-upgrade manually to retry."
Otherwise, use AskUserQuestion:
If "Yes, upgrade now": Proceed to Step 2.
If "Always keep me up to date":
~/.claude/skills/pstack/bin/pstack-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=~/.pstack/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 ~/.pstack/config.yaml for automatic upgrades."
If "Never ask again":
~/.claude/skills/pstack/bin/pstack-config set update_check falseTell user: "Update checks disabled. Run ~/.claude/skills/pstack/bin/pstack-config set update_check true to re-enable."
Continue with the current skill.
if [ -d "$HOME/.claude/skills/pstack/.git" ]; then
INSTALL_TYPE="global-git"
INSTALL_DIR="$HOME/.claude/skills/pstack"
elif [ -d "$HOME/.pstack/repos/pstack/.git" ]; then
INSTALL_TYPE="global-git"
INSTALL_DIR="$HOME/.pstack/repos/pstack"
elif [ -d ".claude/skills/pstack/.git" ]; then
INSTALL_TYPE="local-git"
INSTALL_DIR=".claude/skills/pstack"
elif [ -d ".agents/skills/pstack/.git" ]; then
INSTALL_TYPE="local-git"
INSTALL_DIR=".agents/skills/pstack"
elif [ -d ".claude/skills/pstack" ]; then
INSTALL_TYPE="vendored"
INSTALL_DIR=".claude/skills/pstack"
elif [ -d "$HOME/.claude/skills/pstack" ]; then
INSTALL_TYPE="vendored-global"
INSTALL_DIR="$HOME/.claude/skills/pstack"
else
echo "ERROR: pstack 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/garrytan/pstack.git "$TMP_DIR/pstack"
mv "$INSTALL_DIR" "$INSTALL_DIR.bak"
mv "$TMP_DIR/pstack" "$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_PSTACK=""
if [ -n "$_ROOT" ] && [ -d "$_ROOT/.claude/skills/pstack" ]; then
_RESOLVED_LOCAL=$(cd "$_ROOT/.claude/skills/pstack" && pwd -P)
_RESOLVED_PRIMARY=$(cd "$INSTALL_DIR" && pwd -P)
if [ "$_RESOLVED_LOCAL" != "$_RESOLVED_PRIMARY" ]; then
LOCAL_PSTACK="$_ROOT/.claude/skills/pstack"
fi
fi
echo "LOCAL_PSTACK=$LOCAL_PSTACK"If LOCAL_PSTACK is non-empty, update it by copying from the freshly-upgraded primary install (same approach as README vendored install):
mv "$LOCAL_PSTACK" "$LOCAL_PSTACK.bak"
cp -Rf "$INSTALL_DIR" "$LOCAL_PSTACK"
rm -rf "$LOCAL_PSTACK/.git"
cd "$LOCAL_PSTACK" && ./setup
rm -rf "$LOCAL_PSTACK.bak"Tell user: "Also updated vendored copy at $LOCAL_PSTACK — commit .claude/skills/pstack/ when you're ready."
If ./setup fails, restore from backup and warn the user:
rm -rf "$LOCAL_PSTACK"
mv "$LOCAL_PSTACK.bak" "$LOCAL_PSTACK"Tell user: "Sync failed — restored previous version at $LOCAL_PSTACK. Run /pstack-upgrade manually to retry."
mkdir -p ~/.pstack
echo "$OLD_VERSION" > ~/.pstack/just-upgraded-from
rm -f ~/.pstack/last-update-check
rm -f ~/.pstack/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:
pstack 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 /pstack-upgrade (not from a preamble):
~/.claude/skills/pstack/bin/pstack-update-check --force 2>/dev/null || \
.claude/skills/pstack/bin/pstack-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_PSTACK).
If LOCAL_PSTACK is empty (no local vendored copy): tell the user "You're already on the latest version (v{version})."
If LOCAL_PSTACK is non-empty, compare versions:
PRIMARY_VER=$(cat "$INSTALL_DIR/VERSION" 2>/dev/null || echo "unknown")
LOCAL_VER=$(cat "$LOCAL_PSTACK/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/pstack/ 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."
© no-session, 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 pstack-upgrade of no-session/pstack.
Open the folder on GitHubat commit 9a24d14
Pstack 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 |
|---|---|---|---|---|---|---|
| Pstack Upgrade this skillno-session/pstack | 131 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.4k | 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.
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
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.
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
no-session/pstack
Fast headless browser for QA testing and site dogfooding. An agent skill from no-session/pstack.
no-session/pstack
Import cookies from your real Chromium browser into the headless browse session.
no-session/pstack
Launch real Chrome controlled by pstack with the Side Panel extension auto-loaded.
no-session/pstack
Chief Security Officer mode. An agent skill from no-session/pstack.
no-session/pstack
Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate.
no-session/pstack
Post-deploy monitor monitoring. An agent skill from no-session/pstack.
Works with
Categories
Upgrade pstack to the latest version. An agent skill from no-session/pstack. Pstack Upgrade is an agent skill from no-session/pstack. Upgrade pstack to the latest version.
Pstack Upgrade fits situations like: asked to upgrade pstack; get latest version.
Run `npx skills add no-session/pstack --skill pstack-upgrade -a claude-code`. Or copy the skill folder (pstack-upgrade in no-session/pstack) into .claude/skills/pstack-upgrade in your project. Claude Code loads it when a task matches its description.
Run `npx skills add no-session/pstack --skill pstack-upgrade -a codex`. Or copy the skill folder (pstack-upgrade in no-session/pstack) into .agents/skills/pstack-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 no-session/pstack --skill pstack-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/pstack-upgrade, .gemini/skills/pstack-upgrade, .github/skills/pstack-upgrade and .opencode/skills/pstack-upgrade in your project.
Going by SKILL.md and its folder, Pstack 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.
Pstack 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 Pstack Upgrade: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
no-session (a GitHub user) maintains it in no-session/pstack, which has 131 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on March 30, 2026.
Source: no-session/pstack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.