open-pr

Source excerpt starting at line 1.

1---2name: open-pr3description: 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.4allowed-tools: Bash, Read, AskQuestion5---6 7# Open Pull Request8 9Opens a draft PR from the current branch following Storybook conventions.10 11## Workflow12 13### 1. Gather context14 15Run in parallel: `git status`, `git diff`, `git log --oneline <base>...HEAD` (after step 2), `git branch -vv`.16 17Push first if needed: `git push -u origin HEAD`.18 19### 2. Detect base branch20 21```bash22git fetch origin23bash .agents/skills/open-pr/scripts/detect-base-branch.sh24```25 26Detects 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.27 28### 3. Ask for labels29 30Use **AskQuestion** for three questions. Options from `.github/PULL_REQUEST_TEMPLATE.md`:31 32| Question   | Options                                                                                                                  |33| ---------- | ------------------------------------------------------------------------------------------------------------------------ |34| CI label   | `ci:normal`, `ci:merged`, `ci:daily`                                                                                     |35| QA label   | `qa:needed`, `qa:skip`                                                                                                   |36| Type label | `bug`, `maintenance`, `dependencies`, `build`, `cleanup`, `documentation`, `feature request`, `BREAKING CHANGE`, `other` |37 38Verify the available labels with the PR template.39 40### 4. Draft title and body41 42**Title:** `[Area]: [Description]` — see the `pr` skill for format and examples.43 44**Body:** Read `.github/PULL_REQUEST_TEMPLATE.md`. Copy it **exactly** (keep all HTML comments). Fill in:45 46- `Closes #` when an issue is linked47- **What I did**48- Testing checkboxes and mandatory manual-testing steps (or state why none is needed)49- Documentation checkboxes when applicable50- Leave maintainer checklist items unchecked51 52### 5. Create the PR53 54```bash55gh pr create \56  --draft \57  --base "<detected-base>" \58  --title "<Area>: <Description>" \59  --body "$(cat <<'EOF'60<FILLED_TEMPLATE>61EOF62)" \63  --assignee @me \64  --label "<type>,<ci>,<qa>"65```66 67### 6. Report and offer canary68 69Share the PR URL. Then **AskQuestion**: "Do you want to create a canary release for this PR?"70 71- **Yes** — follow the `canary` skill72- **No** — stop73 74## Notes75 76- Always draft; always assign `@me`.77- For canary details after publishing, see the `canary` skill.78