Creating a Pull Request from a Claude Code Session with gh

Once Claude Code has made a set of changes in a working session, it can commit them and open a pull request against GitHub without leaving that session, using the gh CLI.

Summary

Opening a PR from a session means Claude Code runs the same git and gh commands a developer would type by hand.

There is no separate "Claude Code PR feature" - the gh CLI is GitHub's own official command-line tool, and Claude Code simply invokes it.

That means anything you could do with gh pr create yourself, Claude Code can do as part of finishing a task you asked for.

It also means the PR that results looks completely normal to your team - same title format, same body, same checks running against it.

The only prerequisite is that gh is installed and authenticated in the environment the session is running in.

Recipe

Quick-reference recipe card - copy-paste ready.

git add -A
git commit -m "Add rate limiting to the search endpoint"
git push -u origin HEAD
gh pr create --title "Add rate limiting to the search endpoint" \
  --body "Adds a sliding-window rate limiter to the search endpoint. Fixes #482."

When to reach for this:

• You've asked Claude Code to implement a feature or fix, and the change is ready to review.
• You want the PR title and body written in the same session that made the change, so the description matches the actual diff.
• You're working on a feature branch and want to skip switching to a browser to open the PR.
• You want a repeatable pattern you can also drop into a script or CI step later.

Working Example

#!/usr/bin/env bash
set -euo pipefail
 
# 1. Confirm there is something to commit.
git status --short
 
# 2. Stage and commit the change.
git add -A
git commit -m "Add rate limiting to the search endpoint
 
Adds a token-bucket limiter in middleware/rate-limit.py, applied to
the /api/search route. Limit is 60 requests/minute per API key."
 
# 3. Push the current branch, creating it on the remote if needed.
git push -u origin HEAD
 
# 4. Open the PR against the repository's default base branch.
gh pr create \
  --title "Add rate limiting to the search endpoint" \
  --body "$(cat <<'EOF'
## Summary
- Adds a token-bucket rate limiter to /api/search
- Limit: 60 requests/minute per API key
- Returns HTTP 429 with a Retry-After header when exceeded
 
## Test plan
- [x] Unit tests for the limiter's window boundaries
- [x] Manual test: exceeded the limit locally and confirmed 429 response
 
Fixes #482
EOF
)"
 
# 5. Print the new PR's URL for confirmation.
gh pr view --web=false --json url --jq .url

What this demonstrates:

• Using a heredoc ($(cat <<'EOF' ... EOF)) to pass a multi-paragraph PR body without escaping issues.
• Pushing with -u so the branch is tracked on the remote before gh pr create runs.
• Structuring the PR body with a Summary and Test plan, which matches what most review-oriented teams expect.
• Confirming the result with gh pr view --json url instead of assuming the command succeeded.
• Referencing an issue number (Fixes #482) so GitHub auto-links and closes the issue on merge.

Deep Dive

How It Works

• gh pr create reads the current branch's tracking information to determine what to push against, and the repository's default branch (usually main) as the PR's base unless --base is passed explicitly.
• The command requires the branch to already exist on the remote - git push -u origin HEAD handles that in one step by both pushing and setting up tracking.
• --title and --body are optional; omitting them drops gh into an interactive prompt, which is why session-driven usage almost always supplies both explicitly.
• Once created, gh pr create prints the new PR's URL to stdout, which is useful for a session to report back to you.
• Under the hood, gh authenticates using the token stored by gh auth login, the same credential used for every other gh subcommand.

Flags at a Glance

Bash Notes

# --fill saves typing when the branch has one clean commit whose message
# already reads like a good PR title and body.
git add -A
git commit -m "Add rate limiting to the search endpoint"
git push -u origin HEAD
gh pr create --fill

Gotchas

• Forgetting to push before gh pr create. gh pr create needs the branch to exist on the remote first; if you skip git push -u origin HEAD, the command fails asking you to push. Fix: always push with -u immediately before creating the PR, or let --fill's prompt push it for you.
• Committing directly on the default branch. Opening a PR from main against main doesn't make sense - gh pr create will error or behave unexpectedly. Fix: create and check out a feature branch (git checkout -b <branch-name>) before making changes.
• An expired or missing gh auth token. Commands silently fail with an authentication error if gh auth login was never run or the token expired. Fix: run gh auth status first; re-authenticate with gh auth login if it reports not logged in.
• A PR body with unescaped special characters. Passing --body as a plain quoted string can break on embedded quotes or backticks. Fix: use a heredoc (as in the Working Example) or write the body to a file and pass --body-file.
• Assuming gh pr create opens against the branch you meant. If you're not on the branch you think you are, the PR ends up with the wrong diff. Fix: run git status or git branch --show-current immediately before creating the PR to confirm.
• Opening a PR with no linked issue when your team requires one. Some review processes expect every PR to reference a tracking issue. Fix: include Fixes #<number> or Refs #<number> in the body, and confirm the issue number before running the command.

Alternatives

FAQs

Related

• GitHub Integration Basics - installing and authenticating the gh CLI before using it in a session.
• How Claude Code Fits Into Your GitHub Pull Request Workflow - where opening a PR sits relative to reviewing and responding to feedback.
• Responding to PR Review Comments Automatically - the natural next step once this PR receives feedback.
• GitHub Integration Best Practices - patterns for keeping session-opened PRs safe and reviewable.

Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.