pstack-upgrade

Upgrades pstack installations by detecting install type, running git or vendored updates, and summarizing changelog entries.

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill pstack-upgrade-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pstack-upgrade
Source: https://github.com/no-session/pstack/tree/main/pstack-upgrade
Command: npx skills add https://github.com/no-session/pstack --skill pstack-upgrade-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a CLI skill stack up to date across global and vendored installs is error-prone: you must detect where it lives, handle git versus copied installs, sync local vendored copies, and figure out what changed. This Skill automates the entire upgrade flow for pstack. ## Core Features & Use Cases - Install detection: Identifies global-git, local-git, vendored, and vendored-global installs and applies the correct upgrade strategy for each. - Safe upgrade with rollback: Stashes local changes, backs up vendored directories before replacement, and restores from backup if setup fails. - Update prompts and snoozing: Supports auto-upgrade mode, escalating snooze backoff (24h, 48h, 1 week), and permanent opt-out via config. - Changelog summary: Reads CHANGELOG.md and presents 5-7 user-facing bullets covering everything between the old and new versions. - Use Case: You invoke any pstack skill and see an UPGRADE_AVAILABLE notice; this flow asks whether to upgrade, updates both your global install and the vendored copy in your repo, then shows what is new before continuing your original task. ## Quick Start Ask the assistant to run /pstack-upgrade to check for the latest pstack version and upgrade your installation.

Frequently Asked Questions about pstack-upgrade

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

FAQPage Schema
How do I upgrade pstack to the latest version?

Run /pstack-upgrade, which forces a fresh update check, detects your install type, and upgrades automatically. Git installs use git fetch and reset to origin/main, while vendored installs are replaced with a fresh clone and re-set up.

How does pstack detect global vs vendored installs?

It checks for .git directories in known locations such as ~/.claude/skills/pstack and .claude/skills/pstack. Paths with a .git directory are treated as git installs; directories without one are treated as vendored copies.

Can I enable automatic upgrades for pstack?

Yes. Set auto_upgrade to true via the pstack-config command or choose "Always keep me up to date" when prompted. Future updates then install automatically, with rollback from backup if setup fails.

What happens if the pstack upgrade fails during setup?

For vendored installs, the previous version is restored from the .bak backup directory and a warning is shown. For git installs, stashed local changes can be recovered with git stash pop in the skill directory.

How do I stop pstack update notifications?

Choose "Not now" to snooze with escalating backoff of 24h, 48h, then one week, or choose "Never ask again" to disable update checks entirely. Re-enable later by setting update_check to true with pstack-config.