skills.rest
TrogonStack
TrogonStackOFFICIAL
Explore all skills by this author →
GitHub

gh-enrich-pr-description

Enrich GitHub pull request descriptions by analyzing git history and branch diffs.

10|2|Updated Feb 9, 2026
Search Tags:#automation#git#code review#documentation#pull request#github
One-click install
npx skills add https://github.com/TrogonStack/agentskills --skill gh-enrich-pr-description
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-enrich-pr-description
Source: https://github.com/TrogonStack/agentskills/tree/main/plugins/trogonstack-gh/skills/gh-enrich-pr-description
Command: npx skills add https://github.com/TrogonStack/agentskills --skill gh-enrich-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of sparse or uninformative pull request descriptions by automatically synthesizing git history, commit logs, and related issue context into a comprehensive summary.

Core Features & Use Cases

  • Contextual Synthesis: Analyzes branch diffs and git blame to explain the root cause of changes.
  • Relationship Mapping: Automatically identifies and links related issues, PRs, and dependencies.
  • Stakeholder Identification: Suggests relevant team members to CC based on code ownership and historical involvement.
  • Use Case: Use this when you have finished a complex refactor and need to ensure your PR description clearly explains the technical rationale and impact to reviewers.

Quick Start

Ask the agent to enrich the description of the current pull request by analyzing the branch changes and git history.

Frequently Asked Questions about gh-enrich-pr-description

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

FAQPage Schema
How do I automatically generate a pull request description from git history?▼

You can automatically generate a pull request description by analyzing git history, branch diffs, and related issue metadata to synthesize context-aware summaries that explain the root cause of changes to reviewers.

What is the best way to document a complex refactor for code reviewers on GitHub?▼

The best way to document a complex refactor is to synthesize commit logs and git blame data into a rich PR description, which clearly explains the technical rationale and impact to ensure reviewers understand the changes.

Do I need GitHub CLI integration to enrich pull request descriptions?▼

Yes, GitHub CLI integration is required to fetch PR data and perform repository-level queries needed to analyze branch changes, identify related work, and suggest relevant reviewers for your pull request.

Can I automatically identify related issues and dependencies for a GitHub pull request?▼

You can automatically identify and link related issues, PRs, and dependencies by analyzing branch diffs and related issue metadata, mapping relationships within your software development workflow to provide comprehensive context.

How does code ownership analysis suggest relevant reviewers for a pull request?▼

Code ownership analysis suggests relevant reviewers by examining historical involvement and code ownership data within the repository, identifying team members who should be CC'd based on their past contributions to the changed files.

Related Skills

Explore More Software Engineering Skills→
chcardozchcardoz

create-pr

Push a local Git branch and create a GitHub pull request.

Community
Intermediate
zetaalphavectorzetaalphavector
129

create-pr-description

Generate PR titles, descriptions, and reviewer suggestions from commits and diffs.

Official
Advanced
i3ringiti3ringit
3

git-history-analyzer

Analyze git history to trace file evolution, contributors, and change patterns.

Community
Intermediate
paultyngpaultyng
9

ship-it

Automate Git pre-commit checks, changelog generation, and GitHub pull request updates.

Community
Advanced