skills.rest
lucasmccomb
lucasmccombCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-description

Generate pull request titles and bodies from branch diffs and commits.

1|Updated Mar 19, 2026
Search Tags:#template#commit#github#diff#pr#generate#pull-request
One-click install
npx skills add https://github.com/lucasmccomb/ccgm --skill pr-description-lucasmccomb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/lucasmccomb/ccgm/tree/main/modules/commands-core/skills/pr-description
Command: npx skills add https://github.com/lucasmccomb/ccgm --skill pr-description-lucasmccomb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Produces clear, repository-aligned pull request titles and bodies so callers can separate voice and content creation from publishing and git operations.

Core Features & Use Cases

  • Produces a single-line TITLE and a structured BODY that prioritize user-facing value and align with the repo's PR template or a sensible default.
  • Collects context from branch commits, diffs, linked issues, and existing PRs, samples large diffs, and applies steering text without performing any GitHub mutations.
  • Use cases include drafting new PRs before publishing, rewriting existing PR bodies for clarity, and generating PR text for automation pipelines that handle publishing independently.

Quick Start

Request a PR title and body by providing a PR reference or the current branch plus any short steering notes.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I generate a pull request title and body from branch commits?▼

To generate a pull request from branch commits, the Skill collects branch diffs, commit history, and linked issues to produce a structured TITLE and BODY aligned with the repository's PR template. It samples large diffs and applies steering text without performing any GitHub mutations.

What is the best way to write value-first pull request descriptions?▼

The best way to write value-first pull request descriptions is to extract context from branch diffs and linked issues to produce a single-line TITLE and structured BODY. These outputs prioritize user-facing value and align with the repository's PR template or a sensible default.

Can I use this to rewrite existing PR bodies for clarity?▼

Yes, you can rewrite existing PR bodies for clarity by providing an open pull request reference. The Skill acts as a pure writer separated from publishing flows, analyzing the current context to generate a new structured BODY that improves clarity without performing GitHub mutations.

Does this tool publish changes to GitHub when generating pull request text?▼

No, this tool does not publish changes to GitHub. Pull request text generation acts purely as a writer separated from publishing flows, returning a TITLE and BODY without performing any GitHub mutations or publishing actions, leaving the caller independent to handle publishing operations.

How do PR templates affect generated pull request descriptions?▼

PR templates dictate the structure of generated pull request descriptions by forcing the output to follow the repository's specific formatting requirements. If no template exists, the generation applies a sensible default template to ensure the structured BODY contains basic metadata.

Related Skills

Explore More Software Engineering Skills→
fpindejfpindej
230

create-pr

Create pull requests for Git repositories with commit history analysis and templates.

Community
Advanced
bs-koobs-koo

pull-request

Automates GitHub Pull Request creation from commit history and branch analysis.

Community
Advanced
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate
ulises-jeremiasulises-jeremias
2

dots-workstation-pr-fallback

Generate structured pull request bodies with YAML and Markdown placeholders.

Community
Intermediate