ce-pr-description

Generate pull request titles and bodies from branch diffs or GitHub PRs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill ce-pr-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-pr-description
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/ce-pr-description
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill ce-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of crafting clear, reviewer-focused pull request titles and descriptions by producing a concise conventional-commit-style title and a value-first body derived from the branch diff or a specified GitHub PR.

Core Features & Use Cases

  • Automatic PR framing: Detects current-branch diffs or resolves a provided PR reference and builds a short, outcome-led summary (before/after/scope) appropriate for reviewers.
  • Structured output for automation: Returns a machine-friendly {title, body} pair so callers can apply edits with gh or other automation without interactive prompts.
  • Evidence preservation and fallbacks: Preserves existing Demo/Screenshots blocks when present, classifies commits (feature vs fix-up), and falls back from local git to the GH API when necessary.

Quick Start

Generate a conventional-commit-style title and a value-first body for the current branch's commits, or pass a PR reference like pr:561 to target a specific pull request.

Frequently Asked Questions about ce-pr-description

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

FAQPage Schema
How do I generate a pull request description from a branch diff automatically?

You can generate a pull request description by applying this Skill to your current-branch diff, which extracts commits via git or the GitHub API and returns a structured title and body.

What is a conventional-commit style PR title and how does it help reviewers?

A conventional-commit PR title uses a standardized prefix to indicate the change type, helping reviewers quickly understand the scope and outcome of the pull request before reading the diff.

Can I use the GitHub API to generate a PR description for a specific pull request number?

Yes, you can pass a specific PR reference like pr:561 to target an existing GitHub pull request, and the Skill will fetch the diff via the GH API to generate the title and body.

Does this PR description generator preserve existing screenshots or demo blocks in the body?

Yes, the generator preserves existing Demo and Screenshots blocks found in the current PR body, ensuring visual evidence is maintained while the textual description is updated with a value-first summary.

What is the best way to get a machine-friendly title and body pair for PR automation?

The best way is to use this Skill, which returns a structured {title, body} output pair designed for programmatic application via tools like gh, without requiring interactive prompts or manual edits.

Why does the generated PR body classify commits into features and fix-ups?

Classifying commits into features and fix-ups helps the PR body distinguish primary value-driven changes from minor corrections, producing a clearer, outcome-led summary that prioritizes reviewer understanding.