Verified:GitHub

pr-description

Name: pr-description
Availability: InStock
Author: Xloxn

Generate structured Markdown pull request descriptions for GitHub and GitLab.

7|1|Updated Oct 16, 2025

Search Tags:#git #workflow #code review #documentation #collaboration #pull request #PR

Ready to run

npx skills add https://github.com/xloxn69/AgileFlow --skill pr-description

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/xloxn69/AgileFlow/tree/main/skills/pr-description
Command: npx skills add https://github.com/xloxn69/AgileFlow --skill pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly written pull request descriptions lead to slow, inefficient code reviews, misunderstandings, and delays in merging code, hindering team productivity.

Core Features & Use Cases

Comprehensive PR Structure: Generates a complete PR description with summary, related issues, changes made, and detailed testing instructions.
Pre-Merge Checklist: Includes a checklist for common verification items before merging, ensuring quality and consistency.
Use Case: You've completed the user login feature and are ready to create a pull request. This skill generates a detailed PR description, including a summary, links to stories, a list of changes, and step-by-step testing instructions, making it easy for reviewers.

Quick Start

Use the pr-description skill to create a pull request description for the "shopping cart checkout" feature.

Frequently Asked Questions about pr-description

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

FAQPage Schema

How do I generate a complete pull request description for GitHub or GitLab?▼

Pull request descriptions automate the creation of structured PR bodies with summary, related issues, changes made, and testing instructions. This skill generates ready-to-paste Markdown containing all sections needed for thorough code reviews, reducing manual documentation work and speeding up the review process.

What should a pull request description include for code reviews?▼

A comprehensive pull request description includes a summary of changes, links to related issues, a detailed list of modifications, step-by-step testing instructions, a pre-merge checklist, migration guides if applicable, and screenshots or relevant links. This structure ensures reviewers have all context needed to assess code quality and functionality.

Can I use PR descriptions to coordinate with testing and documentation workflows?▼

Yes. Pull request descriptions can coordinate with testing and documentation agents, embedding testing steps and migration guides directly in the PR body. This integration streamlines handoffs between code review, QA, and documentation teams within your workflow.

How do PR descriptions improve code review efficiency?▼

Poorly written PRs cause slow reviews, misunderstandings, and merge delays. Structured pull request descriptions with clear summaries, detailed changes, and testing instructions reduce reviewer friction, provide necessary context upfront, and accelerate approval cycles by eliminating back-and-forth clarifications.

Do I need to manually format pull request sections like checklists and migration guides?▼

No. Pull request description generation handles formatting automatically, creating pre-merge checklists and migration guides as part of the complete Markdown body. This ensures consistency across all PRs and eliminates repetitive manual template work.