skills.rest
cuozg
cuozgCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-description

Generate structured PR descriptions from changed files via gh pr edit.

Updated Aug 23, 2026
Search Tags:#automation#git#pr#description#code-review#pull-request
One-click install
npx skills add https://github.com/cuozg/oh-my-unity --skill git-description
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-description
Source: https://github.com/cuozg/oh-my-unity/tree/main/skills/git-description
Command: npx skills add https://github.com/cuozg/oh-my-unity --skill git-description

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the creation of clear, structured PR descriptions by analyzing all changed files in a pull request.

Core Features & Use Cases

  • Analyzes all changed files to capture scope and rationale.
  • Generates a structured PR description ready for review or editing.
  • Useful for new PRs, updating stale descriptions, or automation pipelines.

Quick Start

Investigate all changed files in the current PR, generate a structured description using the template, and apply it with gh pr edit.

Frequently Asked Questions about git-description

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

FAQPage Schema
How do I generate a pull request description automatically from changed files?▼

To generate pull request descriptions automatically, this Skill reads diffs via gh pr diff or git diff, analyzes the changed files, and applies a structured template to produce clear documentation ready for code review.

Can I update stale PR descriptions using an automation pipeline?▼

Yes, you can update stale PR descriptions within an automation pipeline by analyzing the current pull request diff and applying the newly generated text with gh pr edit.

How does analyzing changed files help create better code review documentation?▼

Analyzing changed files captures the complete scope and rationale of modifications, ensuring the generated PR description provides accurate context for code review rather than relying on manual entry.

Do I need the GitHub CLI to apply generated PR descriptions to my repository?▼

Yes, applying the generated PR descriptions requires the GitHub CLI, specifically using the gh pr edit command to push the structured template output directly to your pull request.

What is the best way to structure pull request descriptions for new PRs?▼

The best way to structure pull request descriptions is by using a predefined template in references/pr-description-template.md, which organizes the analyzed diffs into a clear, review-ready format.

Does this PR description generator work with standard git diff output?▼

Yes, the PR description generator works with standard git diff output as well as gh pr diff, allowing you to analyze file changes locally or directly from the pull request context.

Related Skills

Explore More Software Engineering Skills→
funsaizedfunsaized
1

review-pr

Review GitHub pull requests for bugs, regressions, missing tests, and risky changes.

Community
Intermediate
Nice-Wolf-StudioNice-Wolf-Studio

code-review

Automate GitHub PR approvals, change requests, and comments via gh CLI.

Official
Intermediate
EONMUNEONMUN
1

deepwork_rules.define

Create DeepWork rule files with YAML frontmatter and trigger patterns.

Official
Basic
wiltaylorwiltaylor

review-pr

Generate structured JSON feedback from pull request diffs.

Community
Intermediate