pull-request-writing

Generate structured pull request titles and descriptions from local code changes.

1|Updated Apr 2, 2026

Search Tags:#git #diff #generate #pull-request #pr-description #code-changes #pr-title

Ready to run

npx skills add https://github.com/thomassloboda/ai-stuff --skill pull-request-writing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pull-request-writing
Source: https://github.com/thomassloboda/ai-stuff/tree/main/skills/pull-request-writing
Command: npx skills add https://github.com/thomassloboda/ai-stuff --skill pull-request-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning local code changes into concise, actionable PRs helps teams review faster and reduces back-and-forth.

Core Features & Use Cases

Generate a targeted PR title that captures the main change
Produce a structured PR description including summary, motivation, risks, validations, and references
Adapt to a worktree, single diff, or batch of changes across branches

Quick Start

Run the PR writing workflow on your current worktree to produce a ready-to-submit PR package.

Frequently Asked Questions about pull-request-writing

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

FAQPage Schema

How do I generate a pull request description from a git diff?▼

You can generate a pull request description from a git diff by processing local worktrees or branch changes to produce a structured PR package with a targeted title, summary, motivation, risks, and validations.

What should a PR description include for faster code reviews?▼

A PR description should include a summary, motivation, risks, validations, rollout notes, and ticket references to help teams review faster and reduce back-and-forth during the approval process.

Can I create a PR title and summary from multiple commits across branches?▼

Yes, you can create a PR title and summary from multiple commits by analyzing diffs across branches, single commits, or a batch of code changes to identify and generate high-signal PR content.

How do I write a structured PR package from local code changes?▼

To write a structured PR package from local code changes, run a workflow on your current worktree that applies deterministic formatting to extract the main change into a title, summary, and rollout notes.

Does generating PR descriptions from diffs require external dependencies?▼

Generating PR descriptions from diffs does not require external dependencies, as the workflow operates directly on local worktrees and code changes without needing additional libraries or tools.

What is the best way to format a pull request for code review?▼

The best way to format a pull request for code review is to align with a recommended PR structure that ensures deterministic formatting, capturing the main change in a high-signal title and structured description.