Programming · Automation
create-pr
/create-pr
Use when creating a pull request, opening a PR, or pushing and creating a PR for an octomux task
For whom
- Author
- shreypaharia ↗
- Repository
- octomux ↗
- Licence
- MIT
- Last repository change
- 27.08.2026
Assessment and security
100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 27.08.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when creating a pull request, opening a PR, or pushing and creating a PR for an octomux task
Original author description
Use when creating a pull request, opening a PR, or pushing and creating a PR for an octomux task
How it works
- Steps
- Notes
Original SKILL.md headings · 102 lines, 526 words
SKILL.md preview
---
name: create-pr
description: Use when creating a pull request, opening a PR, or pushing and creating a PR for an octomux task
---
# Create PR for an octomux task
Create a GitHub pull request directly using `gh pr create`. The octomux dashboard will auto-detect the PR within 30 seconds.
## Steps
1. **Identify the task branch and repo:**
- Ask the user which task, or infer from context
- Get the task details (branch, repo_path, worktree):
```bash
octomux get-task <task-id>
```
- You need `branch`, `repo_path`, and `base_branch`. The task's `base_branch` is the PR base branch. If not set, default to `main`.
2. **Gather context for the PR description:**
Use the task's `base_branch` as `<base>`:
```bash
git -C <worktree> log <base_branch>..HEAD --oneline
git -C <worktree> diff <base_branch>...HEAD --stat
```
3. **Check if branch is pushed and push if needed:**
```bash
# Check if remote tracking branch exists
git -C <repo_path> ls-remote --heads origin <branch>
```
If the branch is not pushed yet, push it:
```bash
git -C <repo_path> push -u origin <branch>
```
If already pushed, check if local is ahead and push any new commits:
```bash
git -C <worktree> status -sb # check if ahead of remote
git -C <repo_path> push origin <branch> # push if ahead
```
4. **Draft the PR title and body, then confirm with the user:**
**Title:** Conventional commit format, under 70 chars, min 10 char description:
```
<type>(<scope>): <description>
```
Types: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `perf`
Examples: `feat(hooks): add permission prompt tracking`, `fix(terminal): clean up orphaned tmux sessions`
**Body:** Must include all three sections — What, Why, and Testing:
```markdown
## What
<Description of what this PR does — summarize the changes>
## Why
<Explanation of why this change is needed — the motivation>
Resolves <link>
## Testing
<How this was tested — commands run, manual verification, etc.>
```
**Linking tickets/issues:**
- If the task was created from a **Jira ticket**, include the Jira link
- If the task was created from a **GitHub issue**, include: `Resolves #<issue-number>`
- Infer the ticket/issue from the branch name. Jira-style keys match `[A-Z][A-Z0-9]+-\d+` (e.g., `feat/PROJ-123-...` -> `PROJ-123`); numeric branches resolve to GitHub issues (`fix/42-...` -> `#42`).
- If no ticket/issue is associated, omit the `Resolves` line
**IMPORTANT: Present the title and body to the user and WAIT for their confirmation before creating the PR.** Do NOT create the PR without explicit user approval. The user may want to adjust the title, description, or add context.
5. **After user confirms, create the PR using `gh`:**
```bash
gh pr create \
--head <branch> \
--base <base_branch> \
--title "<title>" \
--body "<body>" \
--repo <repo_path>
```
6. **Report** — Print the PR URL. The octomux dashboard will auto-detect and link it to the task within ~30 seconds via the PR poller.
## Notes
- Do NOT use the octomux API PR endpoints (`/pr/preview`, `/pr`) — create directly with `gh` for better context and speed
- The dashboard auto-detects PRs by matching the branch name — no manual DB update needed
- If `gh pr create` fails with "already exists", the PR was likely already created
- The task must have a `branch` set (created automatically when octomux starts the task)
- Use `--repo` flag with the repo path so `gh` knows which repo to target
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · shreypaharia/octomux | 100 | MIT |
| wanteddev/montage-web | 100 | MIT |
| niekcandaele/claude-helpers | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| microsoft/aspire | 100 | MIT |
| rolemodel/skills | 100 | MIT |
| moeru-ai/airi | 100 | MIT |
| sakuro/dotfiles | 100 | MIT |
| fcakyon/claude-codex-settings | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 29252cb80442 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create-task
Use when creating an octomux task to dispatch autonomous Claude Code agents for building features, fixing bugs, or any code changes - 90ship-pr
Use to ship a change end-to-end from an octomux task — write a walkthrough, gate on a code review, open the PR, then monitor CI/comments and push fixes, finally refreshing the walkthrough. Heavier than create-pr; use when you want the full review→ship→watch loop, not just opening a PR. - 95create-pull-request
Create a GitHub pull request the user's preferred way. Use whenever opening, creating, or raising a PR with gh. - 100create-pull-request
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository. - 100v1-pr
Use when explicitly pushing local work or opening a draft pull request. Triggers on "ship it", "create PR", "open PR", or "/v1-pr". - 90submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.