Writing Pull Requests

Generate GitHub Pull Request titles and descriptions with imperative verbs and motivation-driven context.

5|1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/notorious-ai/claude-plugins --skill writing-pull-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Writing Pull Requests
Source: https://github.com/notorious-ai/claude-plugins/tree/main/github-author/skills/writing-pull-requests
Command: npx skills add https://github.com/notorious-ai/claude-plugins --skill writing-pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and examples (resource) components.

What problem does it solve?

This Skill helps you write clear, concise, and informative Pull Request titles and descriptions that effectively communicate the purpose and impact of your code changes, leading to faster and more productive code reviews.

Core Features & Use Cases

  • Imperative Titles: Learn to craft titles that describe repository transformation, not developer actions.
  • Contextual Descriptions: Understand how to surface hidden context, constraints, and rationale behind your changes.
  • Use Case: Before submitting a complex feature, use this Skill to ensure your PR title clearly states what the repository will do differently, and your description explains the "why" behind your implementation choices, making it easy for reviewers to understand and approve.

Quick Start

Use the writing pull requests skill to draft a title and description for a PR that adds rate limiting to authentication endpoints.

Frequently Asked Questions about Writing Pull Requests

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

FAQPage Schema
How do I write a good GitHub pull request title and description?

To write a good pull request, use imperative titles that describe repository transformations and craft descriptions that surface the motivation and rationale behind your code changes for faster review.

What should be included in a pull request description for code review?

A pull request description should include the hidden context, constraints, and rationale behind your implementation choices to communicate the purpose and impact of your changes effectively to reviewers.

What is the best way to format a PR title for a complex feature?

The best way to format a PR title is using repository-capability verbs to state what the repository will do differently, ensuring the title clearly describes the transformation rather than the developer's actions.

Can I programmatically generate pull request content for a developer workflow?

Yes, you can programmatically generate pull request content by adhering to established conventions for clarity, using repository-capability verbs for titles and motivation-driven context for descriptions.

Why does my pull request take so long to get reviewed?

Pull requests often take long to review when they lack clear titles and informative descriptions that communicate the purpose and impact of the code changes, preventing productive code reviews.

Does this approach to writing pull requests work for any git developer workflow?

Yes, this approach applies to any git developer workflow by adhering to established conventions for clarity and review efficiency, focusing on motivation-driven context and repository transformation verbs.