pr-description

Generate standardized pull request descriptions with structured templates and guidelines.

10|5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Claude-Code-Community-Ireland/claude-code-resources --skill pr-description-claude-code-community-ireland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/Claude-Code-Community-Ireland/claude-code-resources/tree/main/plugins/vibeworks-library/skills/pr-description
Command: npx skills add https://github.com/Claude-Code-Community-Ireland/claude-code-resources --skill pr-description-claude-code-community-ireland

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidelines and templates to ensure pull requests are clear, actionable, and easy for reviewers to understand, improving code quality and review efficiency.

Core Features & Use Cases

  • Standardized PR Titles: Enforces consistent naming conventions for PR titles using type prefixes (feat, fix, chore, etc.).
  • Structured PR Descriptions: Offers templates for detailed PR descriptions, including Summary, Motivation, Changes, Test Plan, and Reviewer Notes.
  • Issue Linking: Guides on how to link PRs to issues for automatic closing or referencing.
  • PR Size & Stacking: Provides best practices for keeping PRs small and managing dependent PRs effectively.
  • Self-Review Checklist: A detailed checklist to help authors prepare their PRs before submission.

Quick Start

Use the pr-description skill to generate a standard pull request description for your changes.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I write a structured pull request description for code review?

A structured pull request description uses templates covering Summary, Motivation, Changes, Test Plan, and Reviewer Notes to make code review clear, actionable, and easy for reviewers to understand.

What's the best way to standardize pull request titles across a development team?

Standardize pull request titles by enforcing consistent naming conventions with type prefixes like feat, fix, or chore, ensuring immediate context clarity and consistent code quality across development teams.

How do I link a pull request to an issue for automatic closing?

Link a pull request to an issue by using specific closing keywords in the PR description, enabling automatic issue tracking integration and efficient referencing for project management.

What should be included in a self-review checklist before submitting a pull request?

A self-review checklist for pull requests should verify code quality, confirm test plans, validate issue linking, and ensure structured descriptions are complete before submission to accelerate review cycles.

How to manage pull request size and stacking for dependent changes?

Manage pull request size and stacking by keeping PRs small and following best practices for dependent PRs, reducing review friction and maintaining efficient collaboration across complex developer workflows.

Can I use these PR guidelines with existing git collaboration workflows?

Yes, these PR guidelines integrate with existing git collaboration workflows by providing structured templates and documentation standards that complement code review processes without requiring new dependencies.