One-click install
npx skills add https://github.com/toobulkeh/claude-whetstone --skill pr-title-toobulkeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-title
Source: https://github.com/toobulkeh/claude-whetstone/tree/main/examples/pr-title
Command: npx skills add https://github.com/toobulkeh/claude-whetstone --skill pr-title-toobulkeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a pull request diff into a reviewer-friendly, one-line title that clearly states what changed and why it matters.

Core Features & Use Cases

  • One-line PR title distillation: Produces a concise title from a given diff focused on review value.
  • Style enforcement: Applies constraints like imperative mood, a maximum length, and no trailing punctuation.
  • Scope sharpening: Encourages the smallest accurate scope to keep titles specific rather than generic.

Quick Start

Ask your coding agent to apply the pr-title skill to the target diff and return only the final PR title.

Frequently Asked Questions about pr-title

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

FAQPage Schema
How do I generate a pull request title from a diff?▼

To generate a pull request title from a diff, you provide the diff to a coding agent that distills the changes into a single-line, reviewer-ready title communicating what changed and why it is worth reviewing.

What is the character limit and style for an imperative mood PR title?▼

An imperative mood PR title must be 50 characters or less with no trailing period, using verb-led phrasing to ensure a reviewer-ready format that communicates changes clearly for code review.

How do I write a concise PR title for a small bug fix or scoped refactor?▼

Writing a concise PR title for a small bug fix or scoped refactor requires enforcing the smallest accurate scope, ensuring the single-line title remains specific rather than generic while preferring verb-led phrasing.

What is the best way to summarize a code diff for a reviewer-friendly title?▼

The best way to summarize a code diff for a reviewer-friendly title is to distill the changes into a one-line, reviewer-ready format focused on review value, applying style constraints like imperative mood and a 50-character limit.

Can I use a coding agent to enforce consistent PR naming across code changes?▼

Yes, you can use a coding agent to enforce consistent PR naming across code changes by applying diff summarization rules that enforce imperative mood, a 50-character limit, and the smallest accurate scope.

Why does my generated PR title need verb-led phrasing and no trailing period?▼

Your generated PR title needs verb-led phrasing and no trailing period because these style enforcement constraints ensure the one-line title is reviewer-ready, consistent, and clearly communicates what changed and why it matters.