# Create Github PR

Create GitHub pull requests using the gh CLI.

- Repository: https://github.com/NVIDIA/OpenShell (20903 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add NVIDIA/OpenShell --skill create-github-pr -g -a claude-code -y`
Codex: `npx skills add NVIDIA/OpenShell --skill create-github-pr -g -a codex -y`
Cursor: `npx skills add NVIDIA/OpenShell --skill create-github-pr -g -a cursor -y`
Gemini CLI: `npx skills add NVIDIA/OpenShell --skill create-github-pr -g -a gemini-cli -y`

## Description

Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create GitHub Pull Request

Create pull requests on GitHub using the `gh` CLI.

## Prerequisites

- The `gh` CLI must be authenticated (`gh auth status`)
- You must have commits on a branch that's pushed to the remote
- Every PR must close an existing issue, except automated dependency updates and build or flaky-test fixes from authors with write access, as described in `CONTRIBUTING.md`. Follow Branch Names in `CONTRIBUTING.md` for contributor branch names.

## Before Creating a PR

### Verify Contributor Access and Issue Acceptance

Before pushing or creating a PR (including a draft), verify the author's access
to the target repository, not their fork. For the authenticated `gh` user:

```bash
gh repo view OWNER/REPO --json nameWithOwner,viewerPermission
gh issue view ISSUE_NUMBER --repo OWNER/REPO --json number,url,labels
```

Authors with verified `WRITE`, `MAINTAIN`, or `ADMIN` access may proceed without
`state:accepted`; keep the issue link and note the missing label. Everyone else
must link at least one target-repository issue and have `state:accepted` on each.
Otherwise, preserve local work and report which issue needs acceptance. A direct
request, roadmap placement, other labels, or vouch status does not bypass this gate.

When acting for another author, verify their permissions. Resolve failed lookups
before proceeding; retry sandbox network failures outside the sandbox before
reporting an authentication problem. Vouch requirements still apply separately.

### Check Config Documentation

If the branch changes gateway TOML parsing, `[openshell.gateway]` fields,
`[openshell.drivers.<name>]` fields, driver config defaults, or Helm rendering
of `gateway.toml`, verify that `docs/how-it-works/gateways/configuration.mdx` is updated
in the same branch. If the change affects user-facing compute-driver setup,
also update `docs/how-it-works/sandboxes/runtimes.mdx` or the relevant
deployment docs.

### Check Agent Infrastructure

The rest: https://github.com/NVIDIA/OpenShell/blob/HEAD/.agents/skills/create-github-pr/SKILL.md