git-pull-request

Name: git-pull-request
Availability: InStock
Author: DataMKTKorea

Generates a pull request body from git commit logs and branch history.

Updated Jan 24, 2026

Search Tags:#git #pull request #commit analysis #branch history #PR generation

Ready to run

npx skills add https://github.com/datamktkorea/agent-skills --skill git-pull-request-datamktkorea

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-pull-request
Source: https://github.com/datamktkorea/agent-skills/tree/main/plugins/dmk-oneteam/skills/git-pull-request
Command: npx skills add https://github.com/datamktkorea/agent-skills --skill git-pull-request-datamktkorea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of polished Pull Request (PR) bodies from git commits and branch history, reducing the manual effort required to write PR content.

Core Features & Use Cases

Commit Analysis: Automatically analyzes commit logs to generate PR titles and descriptions.
Branch History Analysis: Determines the appropriate parent branch for the PR.
Rebase Recommendation: Suggests rebasing if the branch is behind its parent.
Code and Comment Review: Integrates with other skills to review code comments and clean up documentation.
PR Template Adaptation: Fills in the PR template based on the repository's standard or uses a default template.

Quick Start

Generate a PR body for your current branch by typing 'git-pull-request'.

Frequently Asked Questions about git-pull-request

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

FAQPage Schema

How do I automatically generate a pull request from git commit logs?▼

You can automatically generate a pull request by analyzing git commit logs and branch history to create a polished PR body. This process extracts commit messages and diffs against the correct parent branch to formulate the title and description.

What is the best way to analyze branch history for PR generation?▼

Analyzing branch history for PR generation involves comparing your current feature branch against its appropriate parent branch. This comparison identifies the relevant diffs and commit logs needed to populate a comprehensive and accurate pull request body.

Does PR generation work with the GitHub CLI and git?▼

Yes, automated PR generation requires both git and the GitHub CLI (gh) to be installed. Git is used to analyze commit logs and branch history, while the GitHub CLI handles the actual creation of the pull request on your repository.

Can I fill in a standard PR template automatically from commit diffs?▼

Yes, you can automatically fill in a PR template based on your repository's standard format. If a specific template exists, it will be populated using analyzed commit data; otherwise, a default template is used for the pull request body.

How to handle a feature branch that is behind its parent branch before creating a PR?▼

When a feature branch is behind its parent branch, the analysis will recommend rebasing before proceeding. This ensures your pull request contains only the necessary commits and avoids merging outdated code into the main project.

When do I need to review code comments before generating a pull request?▼

Reviewing code comments before generating a pull request is useful when you want to clean up documentation alongside your commit analysis. This step integrates with other tools to ensure the submitted PR body and codebase remain polished and accurate.