New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Create GitHub PR

by NVIDIA in NVIDIA/OpenShell

Create GitHub pull requests using the gh CLI. An agent skill from NVIDIA/OpenShell.

OfficialApache-2.0Auto-check passedDevelopment

Install Create GitHub PR

skills CLI
$ npx skills add NVIDIA/OpenShell --skill create-github-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/OpenShell create-github-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-github-pr .claude/skills/create-github-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-github-pr
GitHub stars
15k
Token cost
~1.9k tokens
SKILL.md length
689 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create GitHub pull requests using the gh CLI. An agent skill from NVIDIA/OpenShell.

  • Works in 2 steps: You're not on main - Never create PRs… → Branch follows naming convention -…
  • The user wants to create a new PR
  • SKILL.md covers Prerequisites, Before Creating a PR, Creating a PR and PR Title Format, plus 4 more sections
  • Calls gh, git and mise; reaches github.com

What it does

Create GitHub PR is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: OpenShell is the safe, private runtime for autonomous AI agents. The licence is Apache-2.0.

When your agent uses it

  • The user wants to create a new PR
  • Submit code for review
  • Open a pull request
  • Keywords - create PR

Example prompts

  • “/create-github-pr”

Requirements

  • Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. You're not on main - Never create PRs directly from main
  2. Branch follows naming convention - Follow Branch Names in CONTRIBUTING.md, including the exceptions for generated branches and private…

What it can do on your machine

Read from SKILL.md and the folder at commit 834b79a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git
    • mise

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create GitHub PR loads about 1.9k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 689 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/OpenShell at commit 834b79a, republished under its Apache-2.0 licence (© NVIDIA). 689 words, ~1,926 tokens.

Download SKILL.mdSave it as .claude/skills/create-github-pr/SKILL.md (or your agent's skills folder).
name
create-github-pr
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.
metadata.internal
true

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 as described in CONTRIBUTING.md. Follow Branch Names in CONTRIBUTING.md for contributor branch names.

Before Creating a PR

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

Use the sync-agent-infra skill's maintenance map to identify related skill updates when the branch changes behavior, commands, or development workflows. Run its full consistency check when the branch adds, removes, or renames skills or crates; changes workflow relationships or skill coverage; modifies issue or PR templates; or changes agent cross-references. Resolve any drift before creating the PR.

Verify the Affected Areas

Use the verification guidance in CONTRIBUTING.md to select checks for the changed files and behavior. Guidance, skills, and template changes need applicable Markdown, YAML, link, and consistency checks. Run Rust or SDK suites when those components or their dependencies can be affected. Shared APIs, schemas, dependencies, and build changes may require broader checks even when component source files are unchanged.

mise run ci and mise run pre-commit are broad convenience tasks, not blanket PR prerequisites. Broaden validation only for a concrete remaining risk or failed check, and report what actually ran.

Verify Branch State

Before creating a PR, verify:

  1. You're not on main - Never create PRs directly from main:

    bash
    # Should NOT be "main"
git branch --show-current

  2. Branch follows naming convention - Follow Branch Names in CONTRIBUTING.md, including the exceptions for generated branches and private security work.

    bash
    # Example: feat/1234-add-pagination/octocat
git branch --show-current
Push Your Branch

Ensure your branch is pushed to the remote:

bash
git push -u origin HEAD

Creating a PR

Basic PR creation (opens editor for description):

bash
gh pr create

With title and body:

bash
gh pr create --title "PR title" --body "PR description"

PR Title Format

PR titles must follow the conventional commit format:

<type>(<scope>): <description>

Types:

  • feat - New feature
  • fix - Bug fix
  • docs - Documentation only
  • refactor - Code change that neither fixes a bug nor adds a feature
  • test - Adding or updating tests
  • chore - Maintenance tasks (CI, build, dependencies)
  • perf - Performance improvement

Scope is typically the component name (e.g., evaluator, cli, sdk, jobs).

Examples:

  • feat(evaluator): add support for custom rubrics
  • fix(jobs): handle timeout errors gracefully
  • docs(sdk): update authentication examples
  • refactor(models): simplify deployment logic
  • chore(ci): update Python version in pipeline
Show full SKILL.md (277 more words)Show less

Every PR except an automated dependency update must close its own issue. Verify that the issue exists, remains open, and covers the PR scope. Automated dependency updates follow the exception in CONTRIBUTING.md. Use Closes #<issue-number> in the body so merge closes it:

bash
gh pr create \
  --title "fix(cli): validate empty requests" \
  --body "## Summary

Validate empty request bodies.

## Related Issue

Closes #123

## Changes

- Return 400 instead of 500"

If the work needs multiple PRs, create a separate closable issue for each PR. A higher-level tracking issue may link the component issues, but no PR should close that tracking issue until all its work is complete. Follow SECURITY.md for vulnerability disclosure. First-time external contributors must be vouched before their PRs are accepted; the vouch check may close unvouched PRs. Check the current vouch process before opening a PR for an external contributor.

Create as Draft

For work-in-progress that's not ready for review:

bash
gh pr create --draft --title "WIP: New feature"
Target a Different Branch

Default target is main. To target a different branch:

bash
gh pr create --base "release-1.0"

PR Description Format

PR descriptions must follow the project's PR template structure:

markdown
## Summary
<!-- 1-3 sentences: what this PR does and why -->

## Related Issue
<!-- Closes #NNN; this issue covers the scope of this PR -->

## Changes
<!-- Bullet list of key changes -->

## Testing
<!-- What testing was done? -->
- [ ] Checks appropriate to the affected code and behavior pass
- [ ] Unit tests added/updated (if applicable)
- [ ] E2E tests added/updated (if applicable)

## Checklist
- [ ] Follows Conventional Commits
- [ ] Commits are signed off (DCO)

Populate the testing checklist based on what was actually run. Check boxes for steps that were completed.

Example PR (Complete)

bash
gh pr create \
  --title "feat(cli): add pagination to sandbox list" \
  --body "$(cat <<'EOF'
## Summary

Add `--page-size` and `--page-token` flags to `openshell sandbox list` for continuation-token pagination.

## Related Issue

Closes #456

## Changes

- Added `page_size` and `page_token` fields to the sandbox list API call
- Default page size is 100, max is 1,000
- Structured responses include `next_page_token`

## Testing

- [x] Relevant CLI format, lint, and unit checks pass
- [x] Unit tests added/updated
- [ ] E2E tests added/updated (if applicable)

## Checklist

- [x] Follows Conventional Commits
- [x] Commits are signed off (DCO)
EOF
)"

Useful Options

OptionDescription
--title, -tPR title (use conventional commit format)
--body, -bPR description
--reviewer, -rRequest review from user
--draftCreate as draft (WIP)
--label, -lAdd label (can use multiple times)
--base, -BTarget branch (default: main)
--head, -HSource branch (default: current)
--webOpen in browser after creation

After Creating

The command outputs the PR URL and number.

Display the URL using markdown link syntax so it's easily clickable:

Created PR [#123](https://github.com/OWNER/REPO/pull/123)
Monitor Workflow Run (Optional)

If the user asks to wait for a green CI before posting the RFR, use this snippet to monitor the workflow run:

bash
# Watch the latest workflow run for the current branch
gh run watch

Or poll manually:

bash
RUN_ID=$(gh run list --branch "$(git branch --show-current)" --limit 1 --json databaseId --jq '.[0].databaseId')
gh run watch "$RUN_ID"

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/create-github-pr of NVIDIA/OpenShell.

Open the folder on GitHubat commit 834b79a

Compare with similar skills

Create GitHub PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create GitHub PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create GitHub PR this skillNVIDIA/OpenShell15k—~1.9kAutomated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from NVIDIA/OpenShell

All 23 skills in this repo

  • Build Openshell Mxc Windows

    NVIDIA/OpenShell

    Official

    Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.

    15k GitHub stars~4.9k tokensUpdated today
    Auto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Debug Inference

    NVIDIA/OpenShell

    Official

    Debug inference clients that use an attached provider and its native endpoint, including hosted APIs and host-local Ollama, vLLM, SGLang, TRT-LLM, LM Studio, or NIM.

    15k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    15k GitHub stars~19k tokensUpdated today
    Auto-check: notes

  • Gator Gate

    NVIDIA/OpenShell

    Official

    Validate and monitor OpenShell GitHub issues and PRs using the gator: state machine.

    15k GitHub stars~19k tokensUpdated today
    Auto-check passed

  • Helm Dev Environment

    NVIDIA/OpenShell

    Official

    Start up, tear down, and configure the local Kubernetes development environment for OpenShell.

    15k GitHub stars~4.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Create GitHub PR

What does Create GitHub PR do?

Create GitHub pull requests using the gh CLI. An agent skill from NVIDIA/OpenShell. Create GitHub PR is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. Create GitHub pull requests using the gh CLI.

When should I use Create GitHub PR?

Create GitHub PR fits situations like: the user wants to create a new PR; submit code for review; open a pull request; keywords - create PR.

How do I install Create GitHub PR in Claude Code?

Run `npx skills add NVIDIA/OpenShell --skill create-github-pr -a claude-code`. Or copy the skill folder (.agents/skills/create-github-pr in NVIDIA/OpenShell) into .claude/skills/create-github-pr in your project. Claude Code loads it when a task matches its description.

How do I install Create GitHub PR in Codex?

Run `npx skills add NVIDIA/OpenShell --skill create-github-pr -a codex`. Or copy the skill folder (.agents/skills/create-github-pr in NVIDIA/OpenShell) into .agents/skills/create-github-pr in your project. Codex loads it when a task matches its description.

Can I use Create GitHub PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/OpenShell --skill create-github-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-github-pr, .gemini/skills/create-github-pr, .github/skills/create-github-pr and .opencode/skills/create-github-pr in your project.

What does Create GitHub PR need to run?

Going by SKILL.md and its folder, Create GitHub PR needs the command-line tools its instructions call (gh, git and mise). Our summary lists: Python 3.

Does Create GitHub PR access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Create GitHub PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create GitHub PR use?

Create GitHub PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create GitHub PR use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create GitHub PR?

Skills that share tags, products or a category with Create GitHub PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create GitHub PR?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/OpenShell, which has 15,188 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.

Source: NVIDIA/OpenShell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.