describe-pr

Generate template-compliant pull request descriptions from PR diffs and metadata.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/claude-code-flow --skill describe-pr-corticalstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe-pr
Source: https://github.com/corticalstack/claude-code-flow/tree/main/.claude/skills/describe-pr
Command: npx skills add https://github.com/corticalstack/claude-code-flow --skill describe-pr-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork and time pressure of writing clear, template-compliant pull request descriptions by turning the PR’s diff and metadata into a structured, scannable summary.

Core Features & Use Cases

  • Template-aware PR documentation: Reads the repository’s PR template (or uses a standard fallback) and fills every required section.
  • Diff-driven content generation: Pulls the PR diff and commit history, then explains what changed and why it matters.
  • Verification checklist handling: Runs verification commands when available and clearly marks unchecked items for manual testing.

Quick Start

Ask to run /describe-pr to generate and save the PR description under flow/prs/ for the PR associated with your current branch, then update the PR on GitHub.

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 diff automatically?

To generate a pull request description from a diff, this Skill analyzes your current PR's diff and metadata, applies the repository's PR template, and saves the structured output to flow/prs/ before updating GitHub.

Can I automatically fill out a GitHub PR template using my commit history?

Yes, you can automatically fill out a GitHub PR template by reading the local PR template file, analyzing commit history and diffs, and populating required sections for user impact, risks, and breaking changes.

How do I create a verification checklist for a GitHub pull request?

Creating a verification checklist for a GitHub pull request involves running available verification commands against the diff, clearly marking unchecked items, and documenting the test status within the PR template sections.

Does this PR documentation tool work without a custom PR template in the repository?

Yes, this PR documentation tool works without a custom PR template by applying a standard fallback template to structure the generated diff analysis, ensuring all required documentation sections are completed.

What is the best way to document breaking changes and user impact in release notes?

The best way to document breaking changes and user impact in release notes is to extract metadata from the PR diff, map the changes to template-compliant sections, and generate a structured summary for GitHub workflows.

How do I update a pull request body on GitHub from the command line?

To update a pull request body on GitHub from the command line, this Skill selects the correct PR for your current branch, saves the generated markdown description locally, and executes gh pr edit to push the update.