pr-description

Generate PR descriptions from repository templates and metadata.

4|1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill pr-description-gtheys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/gtheys/pi-my-rifle-ext/tree/main/skills/pr-description
Command: npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill pr-description-gtheys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates comprehensive PR descriptions that follow repository templates, reducing manual drafting and ensuring consistency across PRs.

Core Features & Use Cases

  • Follows repository PR templates to structure descriptions consistently.
  • Incorporates notes and metadata from PRs to reflect scope, changes, and verification steps.
  • Adapts to updates by regenerating descriptions when the PR evolves.

Quick Start

Describe the current PR using the repository's template to generate a complete description.

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 repository template?

Generate a PR description by reading the repository's standard PR template, gathering PR metadata, and producing a structured description that aligns with verification steps and repository conventions.

Can I automatically fill out GitHub PR templates using PR metadata?

Yes, automate filling out GitHub PR templates by incorporating notes and metadata from PRs to reflect scope, changes, and verification steps consistently across updates.

What is the best way to keep PR descriptions updated as the PR evolves?

Keep PR descriptions updated by regenerating them from the standard notes template as the PR evolves, adapting the structured description to reflect new changes and metadata.

Does this PR description generator work with any repository's standard template?

Yes, it works with any repository using a standard notes or PRs template, reading the existing template structure to produce descriptions that match repository conventions.

How do I ensure my PR description includes repository verification steps?

Ensure PR descriptions include verification steps by reading the repository's PR template and generating a structured description that aligns with the template's required verification conventions.

Why should I use a template-based approach for generating PR descriptions?

Use a template-based approach to reduce manual drafting and ensure consistency across PRs, producing comprehensive descriptions that follow repository conventions and standard formats.