skills.rest
glowingkitty
glowingkittyCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Create a pull request from dev to main using GitHub CLI.

43|2|Updated Jan 25, 2024
Search Tags:#git#pull request#commit analysis#github cli#release drafting#branch comparison
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill create-pr-glowingkitty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill create-pr-glowingkitty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps developers reliably summarize and create a pull request from the dev branch into main, including a well-structured PR description based on the actual commit history.

Core Features & Use Cases

  • Remote change verification: Uses remote refs (origin/main and origin/dev) to avoid stale local branch data and misleading commit counts.
  • Commit analysis by type: Groups commits by conventional commit prefixes (feat, fix, refactor/perf/improve, and other maintenance categories) to produce a human-readable PR narrative.
  • PR creation and optional draft release prep: Creates the PR using the GitHub CLI only when explicitly requested by the user, then offers preparing a draft release via a follow-up step.

Quick Start

Ask the AI to create a pull request from dev into main with a properly formatted description and draft release if you want one.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a pull request from dev to main with an accurate description?▼

Creating a pull request from dev to main requires analyzing differences between remote branches using origin/main and origin/dev. This Skill groups commits by conventional commit prefixes to generate a human-readable PR narrative, then uses the GitHub CLI to create the PR with the specified base and head.

What is the best way to summarize commits for a GitHub pull request?▼

The best way to summarize commits for a GitHub pull request is by grouping messages by conventional commit types like feat, fix, and refactor. This Skill automates that analysis using remote refs to produce a structured, human-readable PR description based on the actual commit history.

Can I use the GitHub CLI to draft a release after raising a PR?▼

Yes, you can use the GitHub CLI to draft a release after raising a PR. Upon explicitly requesting PR creation, this Skill offers a follow-up step to prepare a draft release based on the validated commit scope and branch comparison.

Why does my local commit count look wrong when comparing dev to main?▼

Your local commit count looks wrong when comparing dev to main because local branch data can be stale. This Skill avoids misleading commit counts by verifying changes exclusively through remote refs like origin/main and origin/dev to ensure accurate branch comparison.

Do I need conventional commit prefixes to generate a PR body?▼

Yes, you need conventional commit prefixes like feat, fix, or refactor to generate a structured PR body. This Skill relies on analyzing full commit messages for these conventional types to group changes and produce a human-readable PR narrative.

Related Skills

Explore More Software Engineering Skills→
glowingkittyglowingkitty
43

openmates:pullrequest

Create GitHub pull requests from dev to main with categorized commit descriptions.

Community
Intermediate
tneztnez
2

pr

Creates a pull request from the current branch to main using GitHub CLI.

Community
Intermediate
spencerbeggsspencerbeggs

merge-prep

Squash git feature branch commits into one conventional commit for PR merging.

Community
Advanced
blakecyzeblakecyze
2

kanso-pr

Generate pull request descriptions from commit history and repository templates.

Community
Intermediate