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

Official agent skill

Prepare PR

by NVIDIA in NVIDIA/NeMo-Relay

Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements.

OfficialApache-2.0Auto-check passedDevelopment

Install Prepare PR

skills CLI
$ npx skills add NVIDIA/NeMo-Relay --skill prepare-pr -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay prepare-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/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-pr .claude/skills/prepare-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
prepare-pr
GitHub stars
192
Token cost
~894 tokens
SKILL.md length
453 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements.

  • Implementation without PR preparation
  • SKILL.md covers Checklist, Pull Request Title, Opening A Pull Request and References
  • Calls gh
  • Tasks that involve Pull requests

What it does

Prepare PR is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements. Do not use for code review or implementation without PR preparation.

Its SKILL.md is about 890 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: Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls. The licence is Apache-2.0.

When your agent uses it

  • Implementation without PR preparation
  • Tasks that involve Pull requests

Example prompts

  • “/prepare-pr”

Requirements

  • Python 3

What it can do on your machine

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

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

  • Network

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

Prepare PR loads about 894 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 453 words of instructions outside code blocks.

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

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/NeMo-Relay at commit 16d73b4, republished under its Apache-2.0 licence (© NVIDIA). 453 words, ~894 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-pr/SKILL.md (or your agent's skills folder).
name
prepare-pr
description
Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements. Do not use for code review or implementation without PR preparation.
license
Apache-2.0

Prepare A PR For NeMo Relay

Use this skill at the end of a contributor or maintainer change before opening a pull request. Also use it whenever a user asks to create, open, publish, update, or edit a NeMo Relay pull request, pull request description, or PR body.

If this repo-local guidance conflicts with generic GitHub publishing, connector, or plugin guidance, this skill wins for PR body format, validation language, and review handoff details.

Checklist

  • Branch scope is coherent and reviewable
  • Validation results accurately report checks already run and relevant omissions without widening validation solely for PR preparation
  • Pull request title follows Conventional Commit style and uses the correct type
  • Pull request body follows .github/pull_request_template.md
  • Breaking changes or renamed surfaces are called out explicitly

Pull Request Title

Use Conventional Commit style for PR titles:

text
<type>: <concise imperative summary>

Choose the type from the actual change surface, not from the impact of the review comment or CI outcome. Use fix only for an actual user-facing or runtime/product code bug fix. Never use fix for changes that are not related to product code behavior, including chores, CI configuration, docs, tests, packaging metadata, generated-output handling, or agent/skill guidance.

Common examples:

  • ci: update codecov coverage reporting
  • docs: clarify release workflow
  • enhancement: improve scope configuration
  • chore: refresh generated attribution data
  • skills: add a plugin-authoring guide
  • test: add Python scope regression coverage
  • fix: preserve scope-local middleware cleanup
Show full SKILL.md (226 more words)Show less

Opening A Pull Request

Always use .github/pull_request_template.md as the source of truth for the PR body. Before opening a PR, read the current template and preserve its headings, checkboxes, comments' intent, and related-issue guidance.

This applies both when creating a new PR and when editing an existing PR description. Do not use a generic Summary / Why / Validation body unless the current repository template uses those headings.

When using GitHub CLI, prefer:

bash
gh pr create --template .github/pull_request_template.md

If a tool cannot consume the template directly, create the PR body from the template content and then fill in every visible section before opening the PR. Do not replace the template with a freeform summary.

After creating or editing a PR, fetch the rendered PR body and verify that the template's visible headings and checklist items are still present.

The PR body must include:

  • #### Overview with a concise summary and both contribution confirmation checklist items preserved
  • #### Details with the concrete changes made
  • #### Where should the reviewer start? with the most useful file, test, or design decision
  • #### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to) with an issue reference, or a clear Relates to: none entry when there is no related issue

Only check the contribution confirmation boxes when they are true. If either confirmation cannot be made, stop before opening the PR and surface the blocker.

References

  • CONTRIBUTING.md
  • .github/pull_request_template.md

© 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/prepare-pr of NVIDIA/NeMo-Relay.

Open the folder on GitHubat commit 16d73b4

Compare with similar skills

Prepare 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.

Prepare PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prepare PR this skillNVIDIA/NeMo-Relay192—~894Automated 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/NeMo-Relay

All 30 skills in this repo

  • Draft Release Notes

    NVIDIA/NeMo-Relay

    Official

    Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.

    192 GitHub stars~575 tokensUpdated today
    Auto-check passed

  • Nemo Relay Migrate From Flow

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI…

    192 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Add Middleware

    NVIDIA/NeMo-Relay

    Official

    Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.

    192 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Contribute Docs

    NVIDIA/NeMo-Relay

    Official

    Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.

    192 GitHub stars~710 tokensUpdated today
    Auto-check passed

  • Maintain CI

    NVIDIA/NeMo-Relay

    Official

    Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.

    192 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Nemo Relay Install

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, or maintained framework integrations, or when explaining Hermes Agent's…

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

Works with

Categories

Questions about Prepare PR

What does Prepare PR do?

Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements. Prepare PR is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements.

When should I use Prepare PR?

Prepare PR fits situations like: implementation without PR preparation; tasks that involve Pull requests.

How do I install Prepare PR in Claude Code?

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

How do I install Prepare PR in Codex?

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

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

What does Prepare PR need to run?

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

Does Prepare PR access the network?

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

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

Prepare PR is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prepare PR use?

About 894 tokens (SKILL.md is roughly 3.6k 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 Prepare PR?

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

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 192 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.

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