skills.rest
jhd3197
jhd3197COMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-pr

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

18|2|Updated Feb 6, 2026
Search Tags:#git#commits#generate#code-review#pull-request#pr-description
One-click install
npx skills add https://github.com/jhd3197/CachiBot --skill create-pr-jhd3197
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/jhd3197/CachiBot/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/jhd3197/CachiBot --skill create-pr-jhd3197

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of concise, review-ready pull request titles and descriptions by reading branch commits and diffs so reviewers can quickly understand changes without deep digging.

Core Features & Use Cases

  • Generate an imperative, high-level PR title that summarizes the entire change set.
  • Produce a 2–3 sentence human-friendly summary with a bit of personality to explain the why and what.
  • Optionally include a Highlights section for user-facing changes and a collapsible Technical changes section that enumerates file- and function-level modifications.
  • Use cases include preparing PRs after feature branches, summarizing refactors or bug fixes, and standardizing descriptions for fast code review.

Quick Start

Read the branch commits and diffs, then write a concise PR title and 2-3 sentence description with highlights and technical details and save it to the .pr/YYYY-MM-DD.md file.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I generate a pull request description from git commits and diffs?▼

To generate a pull request description, this skill reads branch commits and diffs to produce a concise human-friendly summary, optional highlights, and a collapsible technical section. It then saves the result into the repository's .pr directory as a markdown file.

What is the best way to write a scannable PR body for a large refactor?▼

The best way to write a scannable PR body for a large refactor is to summarize changes into a short human-friendly summary and a collapsible Technical changes section. This skill enumerates file- and function-level modifications so reviewers can understand changes without deep digging.

Can I create a standard PR title and summary directly from my feature branch?▼

Yes, you can create a standard PR title and summary directly from your feature branch. This skill generates an imperative, high-level PR title and a 2-3 sentence description with personality to explain the why and what of your changes.

Does generating PR descriptions this way include user-facing highlights?▼

Yes, generating PR descriptions this way optionally includes a Highlights section for user-facing changes. It structures the PR body with a concise summary, highlights, and a detailed technical section to ensure review-ready output.

How to format code review summaries for fast reading without manual writing?▼

To format code review summaries for fast reading without manual writing, this skill reads git diffs and commits to produce concise summaries and technical details. It standardizes the description and saves it to a .pr/YYYY-MM-DD.md file for immediate use.

Related Skills

Explore More Software Engineering Skills→
datamktkoreadatamktkorea

git-pull-request

Generates a pull request body from git commit logs and branch history.

Official
Advanced
assertchrisassertchris
2

custom-submit-pr

Create a GitHub pull request with the gh CLI and assign it to assertchris.

Community
Intermediate
liumeixinliumeixin
4

requesting-code-review

Automate code review with static analysis and an independent reviewer subagent.

Community
Advanced
yamato0811yamato0811

pull-request-creator

Summarize Git branch diffs and draft a pull request targeting develop.

Community
Basic