skills.rest
wpfleger96
wpfleger96COMMUNITY
Explore all skills by this author →
GitHub

pr-creator

Generate GitHub pull request descriptions from git history and code changes.

9|Updated Aug 15, 2025
Search Tags:#automation#git#github#code-review#pull-request#pr-generation
One-click install
npx skills add https://github.com/wpfleger96/ai-rules --skill pr-creator-wpfleger96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/wpfleger96/ai-rules/tree/main/src/ai_rules/config/skills/pr-creator
Command: npx skills add https://github.com/wpfleger96/ai-rules --skill pr-creator-wpfleger96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating clear, structured PR descriptions by analyzing git history and code changes, reducing manual drafting time.

Core Features & Use Cases

  • Generate comprehensive PR descriptions that summarize changes, rationale, and impact
  • Differentiate between draft and regular PR modes and automatically collect related issue references
  • Integrate with git histories, diffs, and GitHub workflows to streamline code reviews

Quick Start

Provide a high-quality PR description for the current branch by analyzing git history and changes, then publish through your GitHub workflow.

Frequently Asked Questions about pr-creator

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 commit history?▼

You can automatically generate GitHub pull request descriptions by analyzing git history and code diffs to extract change summaries, rationale, and impact. This approach uses commit messages to classify PR types and populate a structured template with linked issue references.

Can I create a draft pull request automatically from my git branch changes?▼

Yes, you can create a draft pull request automatically by differentiating between draft and regular PR modes during generation. The process analyzes your branch's code changes and git history to populate the description template before publishing through your GitHub workflow.

What is the best way to structure a pull request summary for a code review?▼

The best way to structure a pull request summary for code review is using a template-driven workflow that highlights changes, context, and references. It automatically extracts diffs, classifies the PR type from commit messages, and generates a comprehensive body.

Does automated PR generation work with existing GitHub workflows and issue references?▼

Yes, automated PR generation integrates with existing GitHub workflows by collecting related issue references and analyzing git histories. It performs pre-flight checks and generates descriptions that fit directly into your established software development process.

Why do my pull request descriptions lack context and rationale from my code changes?▼

Pull request descriptions often lack context when drafted manually without analyzing the full git history and diffs. Automating this process extracts the rationale and impact directly from code changes and commit messages to build a comprehensive summary.

Related Skills

Explore More Software Engineering Skills→
ebinnionebinnion
5

testing-plan-from-history

Analyze git history and PRs to generate testing instructions for changed files.

Community
Intermediate
jaypatrickjaypatrick

create-pull-request

Create GitHub pull requests with validated prerequisites and gh CLI.

Community
Intermediate
jporrejporre
6

b10-ship

Orchestrate GitHub issue workflows from triage through code review.

Community
Advanced
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic