skills.rest
tfunk1030
tfunk1030COMMUNITY
Explore all skills by this author →
GitHub

describe_pr

Generate GitHub PR descriptions from repository templates using PR metadata and diffs.

1|Updated Jan 2, 2026
Search Tags:#automation#workflow#template#documentation#pr#description#pull-request
One-click install
npx skills add https://github.com/tfunk1030/vibe --skill describe-pr-tfunk1030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: describe_pr
Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/describe_pr
Command: npx skills add https://github.com/tfunk1030/vibe --skill describe-pr-tfunk1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams automate the creation of comprehensive PR descriptions that adhere to repository templates, saving time and reducing boilerplate.

Core Features & Use Cases

  • Template-aware: Reads the repository's PR description template and populates it with context.
  • Context gathering: Inspects PR metadata, diffs, commits, and base branch to craft an accurate description.
  • Guided verification: Integrates a checklist-based verification to ensure all steps are covered before submission.

Quick Start

Provide a PR number or URL to describe and the tool will generate a complete PR body.

Frequently Asked Questions about describe_pr

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

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

To generate a pull request description from a template, provide a PR number or URL and the tool reads the repository template at thoughts/shared/pr_description.md, populating it with gathered PR metadata, diffs, and commits to create a complete PR body.

What information does an automated PR description generator use to fill in the template?▼

An automated PR description generator inspects PR metadata, code diffs, commit history, and the base branch to gather context for accurately populating the repository template fields.

Do I need a specific file structure to automate PR documentation in my development workflow?▼

Yes, you need a specific file structure. The automation reads your PR template from the thoughts/shared/pr_description.md path and writes the generated output to thoughts/shared/prs/{number}_description.md.

Can I use a checklist to verify my pull request before submission?▼

Yes, the PR description generation process integrates a checklist-based verification mechanism to ensure all required steps are covered before you submit the pull request.

What is the best way to ensure consistent PR documentation across multiple GitHub repositories?▼

The best way to ensure consistent PR documentation is to use template-aware automation that reads a standardized PR template and applies it uniformly across all pull requests in your software development workflow.

Related Skills

Explore More Software Engineering Skills→
BrightBlockBrightBlock
2

ci_describe_pr

Generate a PR description from repository data and a template.

Official
Intermediate
lambdamechaniclambdamechanic
2

landing-the-plane

Automate verification of code completion and readiness for review in Git-based workflows.

Official
Intermediate
gittowergittower
413

pr-review

Create a structured GitHub pull request review draft with inline comments.

Official
Advanced
propstreetpropstreet
2

update-pr

Generate structured Markdown PR summaries from branch changes and update via gh CLI.

Official
Advanced