describe_pr

Generate PR descriptions from gh diffs and commits using the pr_description.md template.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill describe-pr-brightblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe_pr
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/describe_pr
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill describe-pr-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate comprehensive PR descriptions that align with the repository's pr_description.md template, ensuring consistency and completeness for code reviews and automated checks.

Core Features & Use Cases

  • Template-driven description: Reads and applies the repository's pr_description.md structure to describe PR purpose, changes, verification steps, and metadata.
  • Automated checks integration: Integrates with gh pr view and gh pr diff to assemble accurate details, including checks and verification status.
  • Use Case: When asked to describe an existing PR, it compiles a full narrative with diffs, commits, base branch, and metadata and saves it to thoughts/shared/prs/{number}_description.md for later update.

Quick Start

Describe a target PR by generating a complete description that follows the repository's pr_description.md template and save it to thoughts/shared/prs/{number}_description.md.

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 from a template automatically?

To generate a pull request description from a template, this Skill reads your repository's pr_description.md structure, collects diff and commit metadata via gh, and outputs a complete narrative ready for code review.

What's the best way to automate code review summaries for existing pull requests?

Automating code review summaries involves gathering base branch details, commits, and verification results. This Skill compiles these elements into a structured PR description saved to thoughts/shared/prs/ for later use.

Does generating PR descriptions require the GitHub CLI?

Generating PR descriptions requires the GitHub CLI to fetch metadata. It uses gh pr view and gh pr diff commands to assemble accurate diff and commit details for the final output.

Can I use repository templates to structure pull request details and verification steps?

You can use repository templates to structure pull request details. The Skill applies your pr_description.md format to organize PR purpose, changes, and verification steps consistently across the team.

How to compile git diffs and commit history into a single ready-to-paste PR description?

Compiling git diffs and commit history into a ready-to-paste PR description is done by collecting data via gh pr diff and gh pr view, then formatting it according to your repository template into a markdown file.

Why are my automated pull request descriptions missing verification checks?

Pull request descriptions may miss verification checks if optional checks are not read. This Skill integrates optional gh checks to assemble accurate details and ensure the verification status is included in the output.