git-pr

Generate pull request titles and markdown descriptions from Git branch differences.

10|2|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/toilahuongg/Shopify-Agents-Kit --skill git-pr-toilahuongg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/toilahuongg/Shopify-Agents-Kit/tree/main/.claude/skills/git-pr
Command: npx skills add https://github.com/toilahuongg/Shopify-Agents-Kit --skill git-pr-toilahuongg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive pull request descriptions by analyzing branch changes, saving developers time and ensuring consistent documentation.

Core Features & Use Cases

  • Automated Change Analysis: Categorizes changes into Features, Fixes, Refactors, Docs, Tests, and Chores.
  • Structured Description Generation: Creates a markdown-formatted PR description including Summary, Changes, Type of Change, Testing, Screenshots, and a Checklist.
  • PR Title Suggestion: Provides a title in the type(scope): description format.
  • Use Case: After completing a set of bug fixes on a feature branch, use this Skill to generate a clear and detailed PR description that outlines the fixes, their impact, and how they were tested, ready for review.

Quick Start

Use the git-pr skill to generate a pull request description for the current branch.

Frequently Asked Questions about git-pr

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 branch changes?

To generate a pull request description from git branch changes, this skill analyzes commit history and diff statistics to categorize changes and format a structured markdown description automatically.

Can I create a PR title and description directly using the GitHub CLI?

Yes, you can create a PR title and description using the GitHub CLI, as this skill supports automated PR creation and suggests a title formatted as type(scope): description based on branch differences.

What is the best way to categorize code changes for a pull request template?

The best way to categorize code changes for a pull request template is to analyze diff statistics, grouping commits into Features, Fixes, Refactors, Docs, Tests, and Chores for comprehensive documentation.

How do I format a comprehensive markdown PR description for code review?

To format a comprehensive markdown PR description for code review, this skill generates structured sections including Summary, Changes, Type of Change, Testing, Screenshots, and a Checklist based on your commit history.

Does this automated PR generation work without specific dependencies?

Yes, this automated PR generation works without specific dependencies, requiring only your git branch differences and commit history to analyze changes and produce a formatted markdown pull request description.

Why should I automate pull request documentation instead of writing it manually?

You should automate pull request documentation to save developer time and ensure consistent formatting by analyzing branch changes and categorizing commits into a structured markdown template for effective review.