describe_pr

Generate pull request descriptions from repository templates and code diffs.

8|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill describe-pr-scooter-lacroix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe_pr
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/meta/describe_pr
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill describe-pr-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive pull request descriptions, ensuring consistency and adherence to repository standards by leveraging predefined templates.

Core Features & Use Cases

  • Automated Description Generation: Creates detailed PR descriptions based on repository templates.
  • Change Analysis: Analyzes code diffs, commit history, and reasoning logs to inform the description.
  • Verification Checklist Management: Automatically checks off verifiable steps in the PR template and notes manual verification needs.
  • Use Case: After completing a feature, use this Skill to generate a PR description that includes a summary of changes, technical details, and verification steps, ready for review.

Quick Start

Use the describe_pr skill to generate a description for the current pull request.

Frequently Asked Questions about describe_pr

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

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

To generate a pull request description, this Skill parses repository-specific templates and analyzes code changes fetched via GitHub CLI. It aggregates commit history and diffs to populate the template, then updates the PR description automatically with the generated summary and technical details.

Can I automate checking off verification checklists in a GitHub PR template?

Automating verification checklists is supported by this Skill. It automatically checks off verifiable steps in the PR template by analyzing the code changes and explicitly notes manual verification needs for items it cannot automatically validate, integrating the results into the final PR description.

Do I need the GitHub CLI to analyze code diffs and commit history for PR documentation?

Yes, the GitHub CLI (gh) is a required dependency to fetch PR details, code diffs, and commit history. This Skill integrates directly with gh to retrieve repository data and aggregate prior reasoning attempts to inform the generated PR documentation.

What's the best way to document manual verification needs in a pull request?

The best way to document manual verification needs is to use this Skill to automatically identify checklist items that cannot be verified through code analysis. It explicitly notes these manual verification requirements within the PR template and updates the description to ensure reviewers know what requires human validation.

How does template-based PR generation handle prior reasoning attempts and code review logs?

Template-based PR generation handles prior reasoning attempts by aggregating reasoning logs alongside commit history and code diffs. This Skill parses these inputs to inform the description generation, ensuring the final PR documentation reflects the analytical context and technical details of the code review process.

When should I not use automated PR description generation for code review documentation?

You should not use automated PR description generation when a repository lacks a predefined PR template, as this Skill relies on parsing repository-specific templates. Additionally, if your code changes require entirely manual narrative documentation outside standard checklist formats, automatic generation may not capture the necessary context.