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

Agent skill

PR

by verl-project in verl-project/verl-vla

Prepare, create, or update a verl-vla pull request following repository conventions.

Apache-2.0Auto-check passedDevelopment

Install PR

skills CLI
$ npx skills add verl-project/verl-vla --skill pr -a claude-code

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

GitHub CLI
$ gh skill install verl-project/verl-vla 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/verl-project/verl-vla.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr .claude/skills/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
pr
GitHub stars
113
Token cost
~859 tokens
SKILL.md length
410 words
Files
2
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepare, create, or update a verl-vla pull request following repository conventions.

  • The user asks to open
  • SKILL.md covers Gather Context, Validate the Change, Compose the PR and Request Final Confirmation, plus 1 more section
  • Calls git and python3
  • Inspect the complete branch diff and existing GitHub edits

What it does

PR is an agent skill from verl-project/verl-vla. Prepare, create, or update a verl-vla pull request following repository conventions. Use when the user asks to open, draft, publish, or revise a PR; inspect the complete branch diff and existing GitHub edits, require final confirmation before creating a branch, pushing, or changing a PR.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: A unified VLA post-training framework for human-in-the-loop data collection, fine-tuning, and reinforcement learning. The licence is Apache-2.0.

When your agent uses it

  • The user asks to open
  • Inspect the complete branch diff and existing GitHub edits
  • Require final confirmation before creating a branch

Example prompts

  • “/pr”

Requirements

  • Python 3

What it can do on your machine

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

    • git
    • python3

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

  • Network

    No URLs in SKILL.md. Its commands use 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

PR loads about 859 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 410 words of instructions outside code blocks.

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

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 verl-project/verl-vla at commit c1de826, republished under its Apache-2.0 licence (© verl-project). 410 words, ~859 tokens.

Download SKILL.mdSave it as .claude/skills/pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pr
description
Prepare, create, or update a verl-vla pull request following repository conventions. Use when the user asks to open, draft, publish, or revise a PR; inspect the complete branch diff and existing GitHub edits, require final confirmation before creating a branch, pushing, or changing a PR.

Do not create branches, push commits, or create or update a pull request until the user confirms the final preview. Never force-push unless the user explicitly requests it.

Gather Context

Read the repository-root CONTRIBUTING.md and .github/PULL_REQUEST_TEMPLATE.md. Inspect:

bash
git status --short
git branch --show-current
git remote -v
git log --oneline origin/main..HEAD
git diff --stat origin/main...HEAD
git diff origin/main...HEAD

Determine the intended base branch; default to main only when the user did not specify another base. Include the complete branch diff, not just the most recent commit.

Search open pull requests for the same issue or change. If the current branch already has a PR, read its current title, body, draft state, review comments, and requested changes before proposing an update. Preserve edits made directly on GitHub instead of rebuilding the body from scratch.

If the current branch is main, propose a focused branch name. Do not create that branch before final confirmation.

Validate the Change

Run checks relevant to the complete PR and record exact results. Run the repository pre-submit check unless the user explicitly narrows validation:

bash
pre-commit run --all-files --show-diff-on-failure --color=always

Do not claim GPU, LIBERO, Isaac, or LeRobot validation ran when the environment did not support it. State what remains unverified.

Compose the PR

Create a title that follows CONTRIBUTING.md, including [BREAKING] or an optional PR-series prefix when applicable. Validate it with:

bash
python3 scripts/check_pr_title.py --title "[module] type: description"

Fill every applicable section of .github/PULL_REQUEST_TEMPLATE.md. Only check checklist items that were actually completed. Make the overview concise, list exact validation commands, explain missing coverage, and include API or usage examples for user-visible changes.

When updating an existing PR, ensure the title and body describe all branch changes while retaining useful user-authored content.

Show full SKILL.md (159 more words)Show less

Request Final Confirmation

Before any branch creation, push, PR creation, or PR update, show the user:

  • Base and head branches, including a proposed branch name when needed.
  • Commits and files included in the complete PR diff.
  • Proposed title and full body.
  • Checks run, results, and anything unverified.
  • Whether the PR will be draft or ready for review.
  • Exact external actions to perform, including the push destination.

Wait for explicit confirmation. The initial request starts preparation but does not replace confirmation of this preview. If the branch, commits, files, title, body, or remote PR changes after the preview, refresh it and request confirmation again.

Create or Update the PR

After confirmation, recheck the branch and worktree, then perform only the approved actions. Push without force. Create the PR against the approved base, or update the existing PR without overwriting concurrent GitHub edits.

Return the PR URL, final title, base and head branches, draft state, checks run, and remaining worktree state.

© verl-project, 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

SKILL.md and 1 other file in .agents/skills/pr of verl-project/verl-vla.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit c1de826

Compare with similar skills

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.

PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR this skillverl-project/verl-vla113—~859Automated 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 yesterday
    DevelopmentAuto-check passed

More from verl-project/verl-vla

  • Commit

    verl-project/verl-vla

    Synchronize the current tracked branch, then prepare and create a local Git commit following verl-vla conventions.

    113 GitHub stars~1.2k tokensUpdated 27 days ago
    Auto-check passed

  • Issue

    verl-project/verl-vla

    Prepare, create, or update verl-vla GitHub issues following repository conventions.

    113 GitHub stars~1.1k tokensUpdated 27 days ago
    Auto-check passed

Works with

Categories

Questions about PR

What does PR do?

Prepare, create, or update a verl-vla pull request following repository conventions. PR is an agent skill from verl-project/verl-vla. Prepare, create, or update a verl-vla pull request following repository conventions.

When should I use PR?

PR fits situations like: the user asks to open; inspect the complete branch diff and existing GitHub edits; require final confirmation before creating a branch.

How do I install PR in Claude Code?

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

How do I install PR in Codex?

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

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

What does PR need to run?

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

Does PR access the network?

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

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

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

About 859 tokens (SKILL.md is roughly 3.4k 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 PR?

Skills that share tags, products or a category with 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 PR?

verl-project (a GitHub organization) maintains it in verl-project/verl-vla, which has 113 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 11, 2026.

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