تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

create-pr

النجوم٢٠

التفرعات٠

آخر تحديث١٥ مايو ٢٠٢٦ في ٠٩:٥٢

Use when creating a pull request, opening a PR, or pushing and creating a PR for an octomux task

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

ShreyPaharia

ShreyPaharia/octomux

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

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

Identify the task branch and repo:
- Ask the user which task, or infer from context
- Get the task details (branch, repo_path, worktree):
```
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.

Gather context for the PR description:

Use the task's base_branch as <base>:

git -C <worktree> log <base_branch>..HEAD --oneline
git -C <worktree> diff <base_branch>...HEAD --stat

Check if branch is pushed and push if needed:

# Check if remote tracking branch exists
git -C <repo_path> ls-remote --heads origin <branch>

If the branch is not pushed yet, push it:

git -C <repo_path> push -u origin <branch>

If already pushed, check if local is ahead and push any new commits:

git -C <worktree> status -sb  # check if ahead of remote
git -C <repo_path> push origin <branch>  # push if ahead

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:
```
## 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.

After user confirms, create the PR using gh:

gh pr create \
  --head <branch> \
  --base <base_branch> \
  --title "<title>" \
  --body "<body>" \
  --repo <repo_path>

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

المزيد من هذا المستودع

نفس المستودع

send-agent-message

ShreyPaharia/octomux

Use when you need to send a message or instruction to a specific agent running inside a task

2026-06-2120

add-agent

ShreyPaharia/octomux

Use when you need to attach a new Claude Code agent (new tmux window) to an existing running octomux task, sharing the task's worktree and cwd

2026-06-2020

update-task-status

ShreyPaharia/octomux

Use when you want to update the workflow status of an octomux task, add a note, post a progress summary, or link external references (e.g. Jira tickets)

2026-06-2020

create-task

ShreyPaharia/octomux

Use when creating an octomux task to dispatch autonomous Claude Code agents for building features, fixing bugs, or any code changes

2026-06-2020

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

Identify the task branch and repo:

Ask the user which task, or infer from context
Get the task details (branch, repo_path, worktree):
```
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.

Gather context for the PR description:

Use the task's base_branch as <base>:

git -C <worktree> log <base_branch>..HEAD --oneline
git -C <worktree> diff <base_branch>...HEAD --stat

Check if branch is pushed and push if needed:

# Check if remote tracking branch exists
git -C <repo_path> ls-remote --heads origin <branch>

If the branch is not pushed yet, push it:

git -C <repo_path> push -u origin <branch>

If already pushed, check if local is ahead and push any new commits:

git -C <worktree> status -sb  # check if ahead of remote
git -C <repo_path> push origin <branch>  # push if ahead

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:

## 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.

After user confirms, create the PR using gh:

gh pr create \
  --head <branch> \
  --base <base_branch> \
  --title "<title>" \
  --body "<body>" \
  --repo <repo_path>

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