pr-description

Name: pr-description
Availability: InStock
Author: MetaMask

Generate a PR description from git diffs and branch names.

3.0k|1.6k|Updated Jul 18, 2018

Search Tags:#automation #git #template #github #code-review #pull-request #pr-description

Ready to run

npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-description-metamask

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating PR descriptions that consistently follow the MetaMask Mobile PR template is error-prone and time-consuming. This skill automates template population to ensure completeness and consistency.

Core Features & Use Cases

Automates PR description creation: Fills all sections of the repository's PR template from code changes, commits, and diffs.
Context extraction: Analyzes git diffs, branch names, and commit messages to derive rationale and impact.
Template assembly: Generates a complete PR body including Description, Changelog, Related issues, Manual testing steps, and readiness checklists.
Use Case: When preparing a PR, you provide the diff or branch, and this skill outputs a ready-to-submit PR body that aligns with project guidelines.

Quick Start

Provide the diff or branch name and I will generate a complete PR body following the template.

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 PR description from a git diff automatically?▼

To generate a PR description from a git diff, provide the diff or branch name to analyze change context, extract rationale from commits, and assemble a complete PR body aligned with the repository's PR template.

How do I automate filling out a GitHub pull request template from code changes?▼

Automate filling out a GitHub pull request template by analyzing git diffs, branch names, and commit messages to populate sections like Description, Changelog, Related issues, and manual testing steps.

What is the best way to write a PR changelog entry and manual testing steps for code review?▼

The best way to write a PR changelog entry and manual testing steps is to extract impact and context directly from code changes, ensuring the generated PR body passes readiness checks and preserves the official template structure.

Can I use branch names and commit messages to locate related issues for a pull request?▼

Yes, you can use branch names and commit messages to locate related issues, as the PR description generation process analyzes this context to derive rationale and automatically link relevant issues within the PR template.

Does automated PR description generation work with custom repository PR templates?▼

Yes, automated PR description generation works with custom repository PR templates by identifying the change context and assembling the PR template sections to ensure the final description preserves the official template structure.

Why does my generated PR description fail readiness checks before submitting a pull request?▼

Generated PR descriptions may fail readiness checks if the analyzed git diff lacks sufficient context, but the template assembly process is designed to automatically include manual testing steps and a changelog entry to ensure readiness.