skills.rest
yamato0811
yamato0811COMMUNITY
Explore all skills by this author →
GitHub

pull-request-creator

Summarize Git branch diffs and draft a pull request targeting develop.

Updated Jan 6, 2026
Search Tags:#git#development#diff#code-review#branch-management#pull-request#pr-description
One-click install
npx skills add https://github.com/yamato0811/my-agent-skills --skill pull-request-creator-yamato0811
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-creator
Source: https://github.com/yamato0811/my-agent-skills/tree/main/skills/pull-request-creator
Command: npx skills add https://github.com/yamato0811/my-agent-skills --skill pull-request-creator-yamato0811

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users to convert their current branch changes into a clear pull request by summarizing diffs, drafting the PR body, and guiding its creation toward develop.

Core Features & Use Cases

  • Branch verification: Check current branch status, recent commits, and diffs to understand what will be PR'd.
  • PR drafting: Create a concise PR title and description with a summary of changes, rationale, and reviewer notes.
  • PR submission guidance: Provide steps to open a PR toward the develop branch in a typical workflow.

Quick Start

Use the pull-request-creator to generate a PR draft from the current branch by following the steps to review status, summarize changes, and draft PR text.

Frequently Asked Questions about pull-request-creator

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

FAQPage Schema
How do I create a pull request from my current git branch?▼

Drafting a PR involves verifying the current git branch, listing changed files, summarizing diffs, and composing a concise title and description. This produces a ready-to-submit pull request targeting the develop branch for review.

How do I summarize git diffs for a pull request description?▼

Summarizing git diffs for a PR requires listing changed files and recent commits to understand the changes, then composing a description with the summary, rationale, and reviewer notes. This creates a clear PR body for review.

What should be included in a PR description for code review?▼

A PR description for code review should include a concise summary of changes, rationale, and reviewer notes. Drafting this involves verifying the branch status and summarizing diffs to ensure the PR body is clear and ready.

Can I use this to open a PR targeting the develop branch?▼

Yes, this guides opening a PR targeting the develop branch in common workflows. It provides submission steps after verifying branch status, listing changed files, and drafting the PR title and description from your diffs.

Do I need any special git tools to automate PR creation?▼

No special git tools are required to guide PR creation. It relies on standard Git commands and manual steps to verify the working branch, summarize diffs, and produce a high-quality PR ready for review.

Related Skills

Explore More Software Engineering Skills→
OpenSourcePharmaFoundationOpenSourcePharmaFoundation
4

last-session

Summarize recent git commits, branch context, and file status for resumed development.

Community
Basic
PFigsPFigs

parley

Automate GitHub PR feedback by applying fixes or posting inline comments.

Community
Advanced
Ni-BuNi-Bu
4

review

Review branch diffs against base commits and report verified defects.

Community
Advanced
SteelMorganSteelMorgan
87

agent-git-workflow

Manage Git branches, merges, and conditional Pull Requests via GitHub CLI.

Community
Advanced