// Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.
Write the changelog entry for a new minor or major Storybook release. Use when preparing a CHANGELOG.md entry for a X.Y.0 version.
Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.
Checks out a PR (including fork PRs), fixes all linting and TypeScript errors, then pushes the changes back. Use when asked to fix lint, types, or TS errors on a PR.
Upgrade Storybook to a specific version (canary or release). Use this when upgrading Storybook packages in an external app, reproduction, or test project.
Triggers a canary release for a Storybook PR. Use when the user wants to publish a canary version, create a pre-release, or test a PR via npm.
Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.
| name | pr |
| description | Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review. |
| allowed-tools | Bash, Read |
Creates a PR following Storybook conventions.
[Area]: [Description]
CSFFactories: Fix type exportNextjs-Vite: Add supportCLI: Fix automigrate issueAdd these labels to the PR:
Category (required, pick one):
bug - fixes incorrect behaviormaintenance - user-facing maintenancedependencies - upgrading/downgrading depsbuild - internal build/test updates (no changelog)cleanup - minor cleanup (no changelog)documentation - docs only (no changelog)feature request - new featureBREAKING CHANGE - breaks compatibilityother - doesn't fit aboveCI (required, pick one):
ci:normal - standard sandbox set; default for most code changesci:merged - merged sandbox setci:daily - daily sandbox set; use this when changes affect prerelease sandboxes or sandboxes pinned to a framework or React version other than latestci:docs - documentation-only changes (use with documentation category)Read .github/PULL_REQUEST_TEMPLATE.md from the repository root.
Copy that template EXACTLY, including all HTML comments (<!-- ... -->). Fill in the relevant sections based on the changes, but keep all comments intact.
Always create PRs in draft mode:
gh pr create --draft --title "<Area>: <Description>" --body "<FILLED_TEMPLATE>" --label "<category>,<ci>"