/pr-description
Generate a pull request description based on the changes in the current branch.
> /plugin marketplace add storybookjs/react-native > /plugin install react-native-storybook@react-native-storybook
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pr-description
Context preview
What this command does when you run it.
Generate a pull request description based on the changes in the current branch.
Command definition
pr-description.mdGenerate PR Description
Generate a pull request description based on the changes in the current branch.
Instructions
1. First, determine the base branch by checking for a PR or using `next` as default:
gh pr view --json baseRefName --jq '.baseRefName' 2>/dev/null || echo "next"
2. Analyze the changes in this branch compared to the base branch:
- Run `git diff <base>..HEAD --stat` to see changed files
- Run `git diff <base>..HEAD` to see the actual changes
- Run `git log <base>..HEAD --oneline` to see commit messages
3. Read the PR template at `.github/PULL_REQUEST_TEMPLATE.md`
4. Generate a PR description following the template structure:
- **Issue:** Link related issues or write "N/A" with context
- **What I did:** Summarize the changes with bullet points for specific modifications
- **How to test:** Provide clear steps to verify the changes work
- Answer the template questions about examples and documentation
5. Check if a PR exists for this branch:
gh pr view --json number 2>/dev/null
6. If a PR exists, ask the user if they want to update it with the generated description using `gh pr edit`.
Guidelines
- Be specific about version changes (e.g., "1.0.0 → 2.0.0")
- Highlight breaking changes prominently
- Group related changes together
- Keep the description concise but informative
- Use code blocks for commands in "How to test"
Read more
Generate PR Description
Generate a pull request description based on the changes in the current branch.
Instructions
1. First, determine the base branch by checking for a PR or using `next` as default:
gh pr view --json baseRefName --jq '.baseRefName' 2>/dev/null || echo "next"
2. Analyze the changes in this branch compared to the base branch:
- Run `git diff <base>..HEAD --stat` to see changed files
- Run `git diff <base>..HEAD` to see the actual changes
- Run `git log <base>..HEAD --oneline` to see commit messages
3. Read the PR template at `.github/PULL_REQUEST_TEMPLATE.md`
4. Generate a PR description following the template structure:
- **Issue:** Link related issues or write "N/A" with context
- **What I did:** Summarize the changes with bullet points for specific modifications
- **How to test:** Provide clear steps to verify the changes work
- Answer the template questions about examples and documentation
5. Check if a PR exists for this branch:
gh pr view --json number 2>/dev/null
6. If a PR exists, ask the user if they want to update it with the generated description using `gh pr edit`.
Guidelines
- Be specific about version changes (e.g., "1.0.0 → 2.0.0")
- Highlight breaking changes prominently
- Group related changes together
- Keep the description concise but informative
- Use code blocks for commands in "How to test"
A new docs site is being built for Storybook for React Native, you can find it at This readme is for v10, for v9 docs see the v9.1 docs. With Storybook for React Native you can design and develop individual React Native components without running your app.
Repo: storybookjs/react-native