Create a draft pull request from the current branch using the project’s template. The skill checks changes, detects the base branch, gathers label choices, and prepares a title, description, and testing details.
Opens a pull request from the current branch using the PR template. Use when the user asks to open a PR, create a pull request, or invokes /open-pr.
Creates a draft pull request from your current branch using the project’s template. It checks the diff, commit history, and branch state to identify the base branch for comparison. It prepares the title, change description, testing details, and relevant documentation sections, then reports the new PR’s URL.
Use it after implementation when you want to prepare changes for review and fill out the PR template together. It also handles branches created from other feature branches. After checking the template’s available options, it asks you to choose labels for the CI test group, whether QA is needed, and the type of change.
The workflow assumes Storybook conventions. It uses Git, gh, .github/PULL_REQUEST_TEMPLATE.md, and the included base-branch detection script. It pushes the branch if needed, always creates a draft, and assigns the PR to its creator. After creation, it asks whether you want a canary release for testing. If you do, it continues with the separate canary skill.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Opens a draft PR from the current branch following Storybook conventions.
Run in parallel: git status, git diff, git log --oneline <base>...HEAD (after step 2), git branch -vv.
Push first if needed: git push -u origin HEAD.
git fetch origin
bash .agents/skills/open-pr/scripts/detect-base-branch.sh
Detects base in order: tracked upstream → reflog checkout source → closest origin/* ancestor (fewest commits from branch tip to HEAD). Supports telescoped/stacked PRs off feature branches, not only next/main. Skips branches at the same commit as HEAD. Tie-break: feature branch over trunk, then next over main. Falls back to next. Tell the user the result.
Use AskQuestion for three questions. Options from .github/PULL_REQUEST_TEMPLATE.md:
| Question | Options |
|---|---|
| CI label | ci:normal, ci:merged, ci:daily |
| QA label | qa:needed, qa:skip |
| Type label | bug, maintenance, dependencies, build, cleanup, documentation, feature request, BREAKING CHANGE, other |
Verify the available labels with the PR template.
Title: [Area]: [Description] — see the pr skill for format and examples.
Body: Read .github/PULL_REQUEST_TEMPLATE.md. Copy it exactly (keep all HTML comments). Fill in:
Closes # when an issue is linkedgh pr create \
--draft \
--base "<detected-base>" \
--title "<Area>: <Description>" \
--body "$(cat <<'EOF'
<FILLED_TEMPLATE>
EOF
)" \
--assignee @me \
--label "<type>,<ci>,<qa>"
Share the PR URL. Then AskQuestion: "Do you want to create a canary release for this PR?"
canary skill@me.canary skill.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find a trial Storybook package for a specific branch, or trigger its publication when needed. Check release progress and obtain the package reference or commands for creating or upgrading a project with that build.
Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Work through unresolved GitHub pull request reviews one at a time. The skill explains each comment, proposes a fix, asks how to proceed, and handles chosen edits, replies, commits, and thread resolution.