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

Pull Request Title and Body Writer

by openinterpreter in 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.

Apache-2.0Auto-check passedDevelopment

Install Pull Request Title and Body Writer

skills CLI
$ npx skills add openinterpreter/openinterpreter --skill codex-pr-body -a claude-code

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

GitHub CLI
$ gh skill install openinterpreter/openinterpreter codex-pr-body --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/openinterpreter/openinterpreter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/codex-pr-body .claude/skills/codex-pr-body && 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
codex-pr-body
GitHub stars
69k
Used in
2 other repos
Token cost
~1.1k tokens
SKILL.md length
689 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

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.

  • Rewriting a PR description after the implementation changed
  • SKILL.md covers Determining the PR(s), PR Body Contents, Working with Stacks and Sapling
  • Calls git, gh and just
  • Writing a PR body that explains why a change was made

What it does

The target PR can be named explicitly, but usually it is inferred from the branch or commit you are on, using `git branch` together with `gh pr view`. The agent edits the title and body with `gh` after reading the existing body, so key information survives, and it never removes an existing image because the author may have no way to get it back.

Content rules put the reason for the change first, drawing on any motivation discussed in the conversation, then the description of what changed. Only the net change is discussed, not attempts that were later undone. Paths inside the repository are written repo-relative rather than as local absolute paths, confidential details such as codenames and internal URLs are left out, and verification is described without repeating what CI already checks. Formatting uses Markdown, inline code in backticks, fenced blocks and GitHub permalinks to relevant code.

When your agent uses it

  • Rewriting a PR description after the implementation changed
  • Writing a PR body that explains why a change was made
  • Cleaning a PR description of local paths or internal references

Example prompts

  • “Update the PR for my current branch so the body explains why we made this change.”
  • “Rewrite the title and body of my three open PRs to describe only the net change.”
  • “Clean the PR description of local absolute paths, but keep the screenshots.”

Requirements

  • The GitHub CLI (`gh`), authenticated for the repository

What it can do on your machine

Read from SKILL.md and the folder at commit cc054cf. 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
    • gh
    • just

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

  • Network

    Links to these hosts (documentation or services it may open):

    • developers.openai.com
    • sapling-scm.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

Pull Request Title and Body Writer loads about 1.1k tokens when it runs. Until then it costs about 17 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
~17
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 openinterpreter/openinterpreter at commit cc054cf, republished under its Apache-2.0 licence (© openinterpreter). 689 words, ~1,110 tokens.

Download SKILL.mdSave it as .claude/skills/codex-pr-body/SKILL.md (or your agent's skills folder).
name
codex-pr-body
description
Update the title and body of one or more pull requests.

Determining the PR(s)

When this skill is invoked, the PR(s) to update may be specified explicitly, but in the common case, the PR(s) to update will be inferred from the branch / commit that the user is currently working on. For ordinary Git usage (i.e., not Sapling as discussed below), you may have to use a combination of git branch and gh pr view <branch> --repo openai/codex --json number --jq '.number' to determine the PR associated with the current branch / commit.

PR Body Contents

When invoked, use gh to edit the pull request body and title to reflect the contents of the specified PR. Make sure to check the existing pull request body to see if there is key information that should be preserved. For example, NEVER remove an image in the existing pull request body, as the author may have no way to recover it if you remove it.

It is critically important to explain why the change is being made. If the current conversation in which this skill is invoked has discussed the motivation, be sure to capture this in the pull request body.

The body should also explain what changed, but this should appear after the why.

Limit discussion to the net change of the commit. It is generally frowned upon to discuss changes that were attempted but later undone in the course of the development of the pull request. When rewriting the pull request body, you may need to eliminate details such as these when they are no longer appropriate / of interest to future readers.

Avoid references to absolute paths on my local disk. When talking about a path that is within the repository, simply use the repo-relative path.

Avoid references to confidential information including but not limited to codenames or OpenAI-internal URLs.

It is generally helpful to discuss how the change was verified. That said, it is unnecessary to mention things that CI checks automatically, e.g., do not include "ran just fmt" as part of the test plan. Though identifying the new tests that were purposely introduced to verify the new behavior introduced by the pull request is often appropriate.

Make use of Markdown to format the pull request professionally. Ensure "code things" appear in single backticks when referenced inline. Fenced code blocks are useful when referencing code or showing a shell transcript. Also, make use of GitHub permalinks when citing existing pieces of code that are relevant to the change.

Make sure to reference any relevant pull requests or issues, though there should be no need to reference the pull request in its own PR body.

If there is documentation that should be updated on https://developers.openai.com/codex as a result of this change, please note that in a separate section near the end of the pull request. Omit this section if there is no documentation that needs to be updated.

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

Working with Stacks

Sometimes a pull request is composed of a stack of commits that build on one another. In these cases, the PR body should reflect the net change introduced by the stack as a whole, rather than the individual commits that make up the stack.

Similarly, sometimes a user may be using a tool like Sapling to leverage stacked pull requests, in which case the base of the PR may be the a branch that is the head of another PR in the stack rather than main. In this case, be sure to discuss only the net change between the base and head of the PR that is being opened against that stacked base, rather than the changes relative to main.

Sapling

If .git/sl/store is present, then this Git repository is governed by Sapling SCM (https://sapling-scm.com).

In Sapling, run the following to see if there is a GitHub pull request associated with the current revision:

shell
sl log --template '{github_pull_request_url}' -r .

Alternatively, you can run sl sl to see the current development branch and whether there is a GitHub pull request associated with the current commit. For example, if the output were:

  @  cb032b31cf  72 minutes ago  mbolin  #11412
╭─╯  tui: show non-file layer content in /debug-config
│
o  fdd0cd1de9  Today at 20:09  origin/main
│
~
  • @ indicates the current commit is cb032b31cf
  • it is a development branch containing a single commit branched off of origin/main
  • it is associated with GitHub pull request #11412

© openinterpreter, 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 .codex/skills/codex-pr-body of openinterpreter/openinterpreter.

Open the folder on GitHubat commit cc054cf

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in openinterpreter/openinterpreter, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Pull Request Title and Body Writer 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.

Pull Request Title and Body Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pull Request Title and Body Writer this skillopeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
StackUsefulSoftwareCo/executor4.1k—~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
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT

Similar skills

  • Stack

    UsefulSoftwareCo/executor

    User guide for the local squash-safe stack CLI for stacked PR repair.

    4.1k GitHub stars~2.3k tokensUpdated today
    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

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

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

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    60k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from openinterpreter/openinterpreter

All 10 skills in this repo

  • 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
    Auto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    Auto-check passed

  • Remote Executor Integration Tests

    openinterpreter/openinterpreter

    Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them.

    69k GitHub starsUsed in 2 repos~842 tokens
    Auto-check passed

  • Rust Path Types

    openinterpreter/openinterpreter

    Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.

    69k GitHub starsUsed in 2 repos~605 tokens
    Auto-check passed

  • Codex TUI Testing

    openinterpreter/openinterpreter

    Guide for testing Codex TUI interactively

    69k GitHub starsUsed in 2 repos~133 tokens
    Auto-check passed

Works with

Categories

Questions about Pull Request Title and Body Writer

What does Pull Request Title and Body Writer do?

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. The target PR can be named explicitly, but usually it is inferred from the branch or commit you are on, using `git branch` together with `gh pr view`. The agent edits the title and body with `gh` after reading the existing body, so key information survives, and it never removes an existing image because the author may have no way to get it back.

When should I use Pull Request Title and Body Writer?

Pull Request Title and Body Writer fits situations like: rewriting a PR description after the implementation changed; writing a PR body that explains why a change was made; cleaning a PR description of local paths or internal references.

How do I install Pull Request Title and Body Writer in Claude Code?

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

How do I install Pull Request Title and Body Writer in Codex?

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

Can I use Pull Request Title and Body Writer 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 openinterpreter/openinterpreter --skill codex-pr-body -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codex-pr-body, .gemini/skills/codex-pr-body, .github/skills/codex-pr-body and .opencode/skills/codex-pr-body in your project.

What does Pull Request Title and Body Writer need to run?

Going by SKILL.md and its folder, Pull Request Title and Body Writer needs the command-line tools its instructions call (git, gh and just). Our summary lists: The GitHub CLI (`gh`), authenticated for the repository.

Does Pull Request Title and Body Writer access the network?

SKILL.md names 2 domains. As links in the text: developers.openai.com and sapling-scm.com. This is read from the text; nothing was executed.

Is Pull Request Title and Body Writer 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 Pull Request Title and Body Writer use?

Pull Request Title and Body Writer 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 Pull Request Title and Body Writer use?

About 1.1k tokens (SKILL.md is roughly 4.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 Pull Request Title and Body Writer?

Skills that share tags, products or a category with Pull Request Title and Body Writer: Stack (UsefulSoftwareCo/executor, 4.1k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pull Request Title and Body Writer?

openinterpreter (a GitHub organization) maintains it in openinterpreter/openinterpreter, which has 68,517 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

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