github-pr

Analyze branch commits and diffs to draft GitHub pull request titles and descriptions.

2|Updated Oct 10, 2021

Search Tags:#git #developer tools #code review #documentation #pull request #github

Ready to run

npx skills add https://github.com/cenk1cenk2/nvim --skill github-pr-cenk1cenk2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/cenk1cenk2/nvim/tree/main/utils/agents/skills/github-pr
Command: npx skills add https://github.com/cenk1cenk2/nvim --skill github-pr-cenk1cenk2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating clear, concise, and informative GitHub pull request titles and descriptions, ensuring better code review and project understanding.

Core Features & Use Cases

Automated PR Description Generation: Analyzes branch commits and diffs to draft logical descriptions.
Intelligent Title Creation: Generates conventional commit-style titles based on changes.
Template Integration: Fills existing PR templates with relevant information.
Use Case: When you've finished a feature branch, use this Skill to automatically generate a PR title and description that accurately reflects the changes, saving you time and improving clarity for reviewers.

Quick Start

Use the github-pr skill to analyze the current branch and draft a pull request title and description.

Frequently Asked Questions about github-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 branch commits?▼

To generate a GitHub pull request description, this Skill analyzes your current branch commits and diffs to draft logical summaries and conventional commit-style titles automatically.

Can I use this to fill out an existing GitHub PR template with commit details?▼

Yes, you can use this to fill existing GitHub PR templates. It analyzes branch diffs and integrates the relevant change information directly into your predefined template structure.

What's the best way to draft a PR title that follows conventional commit standards?▼

The best way to draft a conventional commit-style PR title is to analyze branch diffs for logical changes. This Skill automatically generates compliant titles based on the detected code modifications.

Do I need Git MCP tools to generate pull request summaries for code review?▼

Yes, you need Git and GitHub MCP tools to gather context and update pull requests. This Skill relies on these integrations to analyze branch commits and apply drafted descriptions.

How does analyzing branch diffs improve code review preparation?▼

Analyzing branch diffs improves code review preparation by extracting logical changes from commits to create clear, concise PR descriptions, ensuring better project understanding for reviewers.

Why does my automated PR description not reflect recent branch changes?▼

If your automated PR description does not reflect recent branch changes, it may lack proper Git MCP integration. The Skill requires these tools to accurately gather current commit context and diff data.