storybook-upgrade

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

Upgrade Storybook to a specific version (canary or release). Use this when upgrading Storybook packages in an external app, reproduction, or test project.

.agents/skills/storybook-upgrade/SKILL.md

Download bundle ↓
next · bf830861 bundle fileScanned 2026-09-14

SKILL.md

389 tokens · o200k_base · 1,510 bytes

Source excerpt starting at line 1.
---name: storybook-upgradedescription: Upgrade Storybook to a specific version (canary or release). Use this when upgrading Storybook packages in an external app, reproduction, or test project.allowed-tools: Bash--- # Storybook Upgrade Upgrades all Storybook packages in a project to a specific version. ## Why this matters for the monorepo This skill is mainly for validating Storybook changes outside this repository. - QA a canary build from a Storybook PR in a downstream app- Reproduce or verify a bug in an external project ## Usage ```bashnpx storybook@<VERSION> upgrade``` ## Examples ### Upgrade to canary version ```bashnpx --yes --allow-remote=all https://pkg.pr.new/storybook@<SHA> upgrade``` ### Upgrade to latest stable ```bashnpx storybook@latest upgrade``` ### Upgrade to specific release ```bashnpx storybook@8.5.0 upgrade``` ## What it does 1. Detects all `@storybook/*` packages in your project2. Upgrades them all to the specified version3. Handles peer dependencies automatically4. Works with npm, yarn, and pnpm ## Important - **DO NOT** manually install storybook packages with `npm add` / `yarn add` / `pnpm add`- Always use `npx storybook@<version> upgrade` to ensure all packages stay in sync- The upgrade command handles version resolution across all storybook packages- **ALWAYS upgrade only 1 major version at a time!**  - Example: 8.x → 9.x → 10.x → canary of 10  - Never skip major versions (e.g., don't go from 8.x directly to 10.x) 
Discovery context

Discovered by repository scan. No exact path reference found in the snapshot’s root AGENTS.md.