codex-pr-body

Updates GitHub pull request titles and bodies using the gh CLI.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill codex-pr-body-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-pr-body
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/codex-pr-body
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill codex-pr-body-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, complete pull request descriptions is repetitive and often skipped, leaving reviewers without context on why a change was made. This Skill drafts and updates PR titles and bodies via the GitHub CLI, capturing the motivation and net change from the current conversation. ## Core Features & Use Cases - PR Body Authoring: Rewrites the title and body of one or more pull requests with gh, explaining why the change was made before what changed. - Stacked PR Support: Handles commit stacks and Sapling-managed stacked pull requests, describing only the net change between base and head rather than the full diff against main. - Content Preservation: Checks the existing PR body first and never removes embedded images or other irreplaceable content. - Use Case: After finishing a feature branch, invoke the Skill to infer the associated PR from the current branch and publish a polished description covering motivation, net change, and verification steps. ## Quick Start Update the pull request for my current branch with a body explaining why this change was made and what it does.

Frequently Asked Questions about codex-pr-body

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a GitHub pull request body from the command line?▼

Use the gh CLI to edit the pull request title and body directly. This Skill infers the PR number from the current branch with gh pr view, then rewrites the body to explain the motivation and net change while preserving existing content like images.

How to write a good pull request description?▼

Explain why the change is being made first, then describe what changed, limiting discussion to the net change of the commits. Include how the change was verified, use Markdown formatting with backticks and permalinks, and reference related issues or pull requests.

Does this work with stacked pull requests in Sapling?▼

Yes, if .git/sl/store is present the repository is managed by Sapling, and the Skill uses sl log or sl sl to find the associated GitHub pull request. The body then describes only the net change between the stacked base and head, not the diff against main.

Will updating a PR body remove existing images or content?▼

No, the Skill explicitly checks the existing pull request body before editing and never removes images, since the author may have no way to recover them. Key existing information is preserved during the rewrite.

What should not be included in a pull request body?▼

Avoid absolute local file paths, confidential information such as codenames or internal URLs, and changes that were attempted but later undone. Also skip mentioning checks that CI runs automatically, like formatting commands.