pr-title-description

Writes plain-language pull request titles and descriptions from full diffs.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-title-description-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-title-description
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/skill-archive/pr-title-description
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-title-description-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request titles and descriptions are often vague, jargon-heavy, or copied from branch names, leaving reviewers unable to understand what actually changed. This Skill reads the full diff of one or more PRs and produces clear, plain-language titles and paste-ready descriptions. ## Core Features & Use Cases - Full-diff behavior inventory: Identifies every independently observable behavior in the diff, including fallbacks and preserved behavior, before writing anything. - Plain-language rewriting: Translates abstract jargon (operation id, registry, adapter) into concrete before/after explanations a non-expert reader can picture. - Direct PR updates: Applies the recommended title and description via gh pr edit and confirms the saved result with gh pr view. - Use Case: You have a PR with a cryptic title like "add operation id to registry". Run this Skill on the PR link to get a title like "Call the icon finder by its name tag instead of asking around" plus a structured description with What this adds, Why, and Verification sections. ## Quick Start Ask the AI to review a pull request link and rewrite its title and description from the full diff in plain language.

Frequently Asked Questions about pr-title-description

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

FAQPage Schema
How do I write a better pull request title and description?▼

Review the full diff and inventory every independently observable behavior, then write a plain-language title describing the before/after change. Follow with a short description covering what it adds, why it is needed, and verification evidence from the PR or CI.

How to update a GitHub PR title and body from the command line?▼

Use gh pr edit with the PR link, passing --title for the new title and --body-file for the description. Then run gh pr view with --json title,body to confirm the saved result matches what you intended.

Can this skill handle multiple pull requests at once?▼

Yes, it accepts one or more pull request links as arguments and applies the same review prompt to each. With no argument, it looks for a PR in the current task, browser, worktree, or GitHub context and asks for a link if none is clear.

What happens if the PR diff cannot be read?▼

The skill explicitly states that it cannot read the PR or full diff and does not propose a title. It never invents behavior, tests, or benefits that are not evidenced in the diff, PR, CI, or its own checks.

Why should PR descriptions avoid jargon like registry or adapter?▼

Jargon assumes the reader already knows the codebase, which excludes reviewers and stakeholders. The skill either drops abstract terms for concrete actions or glosses them immediately with a simple metaphor so the change is clear on first read.