github-pull-request-description

Generates a structured GitHub pull request description from metadata and diffs.

62|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/zerx-lab/rmx --skill github-pull-request-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pull-request-description
Source: https://github.com/zerx-lab/rmx/tree/main/.opencode/skills/github-pull-request-description
Command: npx skills add https://github.com/zerx-lab/rmx --skill github-pull-request-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a concise, human-friendly description for GitHub pull requests, helping teams communicate changes clearly and efficiently.

Core Features & Use Cases

  • Automated PR description: Create a structured summary of changes including features, fixes, and improvements.
  • Diff-assisted context: Optionally incorporate diffs and related metadata to highlight key edits.
  • Use Case: Streamline PR creation in busy projects by generating consistent descriptions from commits and issue references.

Quick Start

Use this skill to generate a PR description from the latest commits and diffs.

Frequently Asked Questions about github-pull-request-description

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

FAQPage Schema
How do I automatically generate a GitHub pull request description from a diff?

You can automatically generate a GitHub pull request description by providing your PR metadata and diffs to a generator. This produces a structured, human-friendly summary highlighting features, fixes, and improvements aligned with project conventions.

Can I create a structured PR summary for bug fixes and documentation updates?

Yes, you can create a structured PR summary for bug fixes and documentation updates. The generation process accepts your PR metadata and diffs to output a concise description communicating these specific changes clearly across software projects.

What is the best way to streamline pull request creation in busy software projects?

The best way to streamline pull request creation in busy software projects is to automate description generation. Using your latest commits and diffs, this approach instantly creates consistent descriptions, reducing manual writing effort and maintaining communication standards.

Do I need to provide diffs and metadata to generate a pull request description?

Yes, you need to provide PR metadata and diffs to generate a pull request description. Incorporating diffs and related metadata allows the generator to highlight key edits and produce a structured summary aligned with your project conventions.

How does diff-assisted context improve automated PR descriptions?

Diff-assisted context improves automated PR descriptions by highlighting key edits and related metadata. Incorporating these diffs allows the generator to produce a concise, structured summary of changes that accurately reflects the actual code modifications.

Are there limitations when generating PR descriptions from commits for feature releases?

Generating PR descriptions from commits for feature releases relies entirely on the provided metadata and diffs. It does not infer unstated context or external dependencies, meaning incomplete commit data will result in a less detailed structured summary.