How is the PR URL returned?

The URL of the created pull request is printed to stdout when the PR is successfully created.

What if I haven’t pushed the current branch?

You'll be prompted to push the branch or to fork the base repository; you can control behavior with --head and related options.

Can I specify the base and head explicitly?

Yes. Use --base to choose the target branch and --head to select the head branch (supports : syntax).

github-pr-open

Scanned

npx machina-cli add skill bryanp/agent-skills/open --openclaw

Files (1)

SKILL.md

4.1 KB

Use the gh pr create command to open a pull request.

Rule: Identity

First use the identity skill to assume the identity of the agent.

Usage

Create a pull request on GitHub.

Upon success, the URL of the created pull request will be printed.

When the current branch isn't fully pushed to a git remote, a prompt will ask where
to push the branch and offer an option to fork the base repository. Any fork created this
way will only have the default branch of the upstream repository. Use `--head` to
explicitly skip any forking or pushing behavior.

`--head` supports `<user>:<branch>` syntax to select a head repo owned by `<user>`.
Using an organization as the `<user>` is currently not supported.
For more information, see <https://github.com/cli/cli/issues/10093>

A prompt will also ask for the title and the body of the pull request. Use `--title` and
`--body` to skip this, or use `--fill` to autofill these values from git commits.
It's important to notice that if the `--title` and/or `--body` are also provided
alongside `--fill`, the values specified by `--title` and/or `--body` will
take precedence and overwrite any autofilled content.

The base branch for the created PR can be specified using the `--base` flag. If not provided,
the value of `gh-merge-base` git branch config will be used. If not configured, the repository's
default branch will be used. Run `git config branch.{current}.gh-merge-base {base}` to configure
the current branch to use the specified merge base.

Link an issue to the pull request by referencing the issue in the body of the pull
request. If the body text mentions `Fixes #123` or `Closes #123`, the referenced issue
will automatically get closed when the pull request gets merged.

By default, users with write access to the base repository can push new commits to the
head branch of the pull request. Disable this with `--no-maintainer-edit`.

Adding a pull request to projects requires authorization with the `project` scope.
To authorize, run `gh auth refresh -s project`.


USAGE
  gh pr create [flags]

ALIASES
  gh pr new

FLAGS
  -a, --assignee login       Assign people by their login. Use "@me" to self-assign.
  -B, --base branch          The branch into which you want your code merged
  -b, --body string          Body for the pull request
  -F, --body-file file       Read body text from file (use "-" to read from standard input)
  -d, --draft                Mark pull request as a draft
      --dry-run              Print details instead of creating the PR. May still push git changes.
  -e, --editor               Skip prompts and open the text editor to write the title and body in. The first line is the title and the remaining text is the body.
  -f, --fill                 Use commit info for title and body
      --fill-first           Use first commit info for title and body
      --fill-verbose         Use commits msg+body for description
  -H, --head branch          The branch that contains commits for your pull request (default [current branch])
  -l, --label name           Add labels by name
  -m, --milestone name       Add the pull request to a milestone by name
      --no-maintainer-edit   Disable maintainer's ability to modify pull request
  -p, --project title        Add the pull request to projects by title
      --recover string       Recover input from a failed run of create
  -r, --reviewer handle      Request reviews from people or teams by their handle
  -T, --template file        Template file to use as starting body text
  -t, --title string         Title for the pull request
  -w, --web                  Open the web browser to create a pull request

INHERITED FLAGS
      --help                     Show help for command
  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format

EXAMPLES
  $ gh pr create --title "The bug is fixed" --body "Everything works again"
  $ gh pr create --reviewer monalisa,hubot  --reviewer myorg/team-name
  $ gh pr create --project "Roadmap"
  $ gh pr create --base develop --head monalisa:feature
  $ gh pr create --template "pull_request_template.md"

Source

git clone https://github.com/bryanp/agent-skills/blob/main/code/github/pr/open/SKILL.mdView on GitHub

Overview

This skill opens a pull request on GitHub using gh pr create. It supports interactive prompts for the PR title and body, options to autofill from commits, and flexible head/base handling (including forks and explicit head syntax). It also covers linking issues and controlling maintainer edits.

How This Skill Works

It invokes gh pr create to open a PR. If the current branch isn’t pushed, you’ll be prompted to push or fork, and you can use --head to specify a head repo/branch. You can provide --title and --body or use --fill to autofill from commits; the base can be set with --base or default logic applies. On success, the PR URL is printed.

When to Use It

You finished work on a feature branch and want to create a PR for review.
You prefer autofilling the PR title/body from commit messages using --fill.
You need to target a specific base branch or work with a fork using --head.
You want to reference and close an issue by including Fixes #123 in the body.
You want to disable maintainers' edits with --no-maintainer-edit or authorize project scope.

Quick Start

Step 1: Ensure you’re on the feature branch and push it to your remote if needed.
Step 2: Run gh pr create with optional --title/--body or use --fill to autofill from commits.
Step 3: Follow prompts (if any) or use the resulting PR URL printed on success.

Best Practices

Push your current branch to a remote before creating the PR.
Use --fill to auto-fill title/body from commits, but rely on explicit --title/--body if needed (title/body take precedence).
Specify --base to ensure the PR targets the correct branch, especially in multi-branch workflows.
If contributing from a fork, use --head with care to select the appropriate head repo/branch.
Review the PR content for clarity before submission and verify issue references like Fixes #123.

Example Use Cases

gh pr create --title "Add user authentication" --body "Implemented login, logout, and session management."
gh pr create --fill
gh pr create --base main --head feature/login-fix
gh pr create --body "Fixes #42" --fill-first
gh pr create --head otheruser:feature/upgrade --title "Enhance API compatibility"

Frequently Asked Questions

Add this skill to your agents