New: 98,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

Agent skill

GitHub PR

by nex-agi in nex-agi/NexRL

Create a GitHub PR from a worktree branch. An agent skill from nex-agi/NexRL.

Apache-2.0Auto-check passedDevelopment

Install GitHub PR

skills CLI
$ npx skills add nex-agi/NexRL --skill github-pr -a claude-code

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

GitHub CLI
$ gh skill install nex-agi/NexRL 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/nex-agi/NexRL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/github-pr .claude/skills/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
github-pr
GitHub stars
119
Token cost
~367 tokens
SKILL.md length
49 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create a GitHub PR from a worktree branch. An agent skill from nex-agi/NexRL.

  • Works in 5 steps: Verify Current Location → Check for Existing PR → Push Branch → …
  • Tasks that involve Git worktrees
  • SKILL.md covers Prerequisites and Workflow
  • Calls gh and git

What it does

GitHub PR is an agent skill from nex-agi/NexRL. Create a GitHub PR from a worktree branch. Use after committing changes.

Its SKILL.md is about 370 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 Git worktrees. It works with GitHub. The repository describes itself as: NexRL is an ultra-loosely-coupled LLM post-training framework. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Git worktrees

Example prompts

  • “/github-pr”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Verify Current Location
  2. Check for Existing PR
  3. Push Branch
  4. Create PR
  5. Update Issue

What it can do on your machine

Read from SKILL.md and the folder at commit 53dcdec. 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

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

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    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

GitHub PR loads about 367 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 49 words of instructions outside code blocks.

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

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 nex-agi/NexRL at commit 53dcdec, republished under its Apache-2.0 licence (© nex-agi). 49 words, ~367 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr/SKILL.md (or your agent's skills folder).
name
github-pr
description
Create a GitHub PR from a worktree branch. Use after committing changes.

GitHub PR Workflow (Worktree-Aware)

Prerequisites

Changes committed via git-commit skill.

Workflow

Step 1: Verify Current Location
bash
git worktree list
pwd
BRANCH_NAME=$(git branch --show-current)
echo "Current branch: $BRANCH_NAME"
Step 2: Check for Existing PR
bash
gh pr list --head "$BRANCH_NAME" --state open --repo "$REPO"

If PR exists, show it and exit.

Step 3: Push Branch
bash
git push --set-upstream origin "$BRANCH_NAME"
Step 4: Create PR
bash
gh pr create \
  --repo china-qijizhifeng/NexRL \
  --base main \
  --head "$BRANCH_NAME" \
  --title "type(scope): description" \
  --body "## Summary
- Key change 1
- Key change 2

## Testing
- [ ] Tests pass (`pytest`)
- [ ] Linting clean (`pylint`, `mypy`)
- [ ] Formatting applied (`black`, `isort`)

## Related Issues
Fixes #ISSUE_NUMBER"

Auto-extract title/body from commit messages. No AI branding.

Step 5: Update Issue
bash
ISSUE_NUM=$(echo "$BRANCH_NAME" | grep -oP 'issue-\K\d+')
if [ -n "$ISSUE_NUM" ]; then
  gh issue edit "$ISSUE_NUM" --repo china-qijizhifeng/NexRL \
    --remove-label "status:in-progress" --add-label "status:review" 2>/dev/null || true
  gh issue comment "$ISSUE_NUM" --repo china-qijizhifeng/NexRL \
    --body "✅ PR created: $(gh pr view --json url -q .url). Ready for review."
fi

© nex-agi, 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 .claude/skills/github-pr of nex-agi/NexRL.

Open the folder on GitHubat commit 53dcdec

Compare with similar skills

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.

GitHub PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub PR this skillnex-agi/NexRL119—~367Automated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Codewhale Landing Workflowcodewhale-hq/Codewhale41k—~1.6kAutomated safety check: PassMIT
Ff Worktreesdamus-io/damus2.1k—~451Automated safety check: PassGPL-3.0
Clean Complete Branchesjtenniswood/espcontrol1.1k—~820Automated safety check: PassCustom licence
Clean Merged Branch Foldersjtenniswood/espcontrol1.1k—~813Automated safety check: PassCustom licence

Similar skills

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Ff Worktrees

    damus-io/damus

    Fast-forward master and every git worktree branch up to a target ref (default github/master), skipping any worktree with unmerged commits.

    2.1k GitHub stars~451 tokensUpdated 26 days ago
    DevelopmentAuto-check passed

  • Clean Complete Branches

    jtenniswood/espcontrol

    Clean up completed Git branches and worktrees for this repository both locally and on GitHub.

    1.1k GitHub stars~820 tokensUpdated today
    DevelopmentAuto-check passed

  • Clean Merged Branch Folders

    jtenniswood/espcontrol

    Clean up local branch worktree folders for this repository after their branches or pull requests have merged to main.

    1.1k GitHub stars~813 tokensUpdated today
    DevelopmentAuto-check passed

  • Fix

    exercism/website

    Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.

    550 GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check: notes

More from nex-agi/NexRL

  • Address PR Comments

    nex-agi/NexRL

    Address GitHub PR review comments. An agent skill from nex-agi/NexRL.

    119 GitHub stars~420 tokensUpdated 21 days ago
    Auto-check passed

  • Fix Issue

    nex-agi/NexRL

    Fix a GitHub issue using git worktree for isolation. An agent skill from nex-agi/NexRL.

    119 GitHub stars~733 tokensUpdated 21 days ago
    Auto-check passed

  • Code Review

    nex-agi/NexRL

    Code review for Python changes in NexRL, following project conventions.

    119 GitHub stars~395 tokensUpdated 21 days ago
    Auto-check passed

  • Git Commit

    nex-agi/NexRL

    Git commit workflow in a worktree with Python linting, formatting, and testing.

    119 GitHub stars~380 tokensUpdated 21 days ago
    Auto-check: notes

  • Testing

    nex-agi/NexRL

    Run tests and linting for NexRL Python project. An agent skill from nex-agi/NexRL.

    119 GitHub stars~350 tokensUpdated 21 days ago
    Auto-check passed

Works with

Categories

Questions about GitHub PR

What does GitHub PR do?

Create a GitHub PR from a worktree branch. An agent skill from nex-agi/NexRL. GitHub PR is an agent skill from nex-agi/NexRL. Create a GitHub PR from a worktree branch.

When should I use GitHub PR?

GitHub PR fits situations like: tasks that involve Git worktrees.

How do I install GitHub PR in Claude Code?

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

How do I install GitHub PR in Codex?

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

Can I use 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 nex-agi/NexRL --skill 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/github-pr, .gemini/skills/github-pr, .github/skills/github-pr and .opencode/skills/github-pr in your project.

What does GitHub PR need to run?

Going by SKILL.md and its folder, GitHub PR needs the command-line tools its instructions call (gh and git).

Does GitHub PR access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is 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 GitHub PR use?

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 GitHub PR use?

About 367 tokens (SKILL.md is roughly 1.5k 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 GitHub PR?

Skills that share tags, products or a category with GitHub PR: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Codewhale Landing Workflow (codewhale-hq/Codewhale, 41k stars), Ff Worktrees (damus-io/damus, 2.1k stars) and Clean Complete Branches (jtenniswood/espcontrol, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub PR?

nex-agi (a GitHub organization) maintains it in nex-agi/NexRL, which has 119 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 17, 2026.

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