git-pr

Generates structured GitHub pull requests following Git Flow branch conventions.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/VelkaressiaBlutkrone/spring-python-llm-exam-mng --skill git-pr-velkaressiablutkrone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/VelkaressiaBlutkrone/spring-python-llm-exam-mng/tree/main/.claude/skills/git-pr
Command: npx skills add https://github.com/VelkaressiaBlutkrone/spring-python-llm-exam-mng --skill git-pr-velkaressiablutkrone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating consistent, well-structured pull requests requires manually analyzing commits, choosing the correct base branch, and writing PR descriptions, which is repetitive and error-prone. ## Core Features & Use Cases - Automatic Base Branch Detection: Inspects local and remote branches to determine whether the project uses Git Flow (develop) or GitHub Flow (main/master) and selects the correct merge target. - Commit-Driven PR Content: Analyzes commit history and diff statistics to generate a Conventional Commits title and a structured PR body with change summaries, file tables, and checklists. - End-to-End PR Creation: Handles uncommitted changes, pushes the branch when needed, and creates the PR via the GitHub CLI, returning the PR URL. - Use Case: After finishing a feature on a feat/board-crud branch, ask for a PR and receive a ready-to-review pull request targeting develop with a formatted description. ## Quick Start Ask the assistant to create a pull request for your current branch, for example by saying "PR 만들어줘" or "create a pull request for my current changes".

Frequently Asked Questions about git-pr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?▼

Use the GitHub CLI with gh pr create, specifying a base branch, title, and body. This skill automates that flow by detecting the base branch, generating the title and body from your commits, pushing the branch, and returning the PR URL.

How do I choose the right base branch for a pull request in Git Flow?▼

In Git Flow, feature branches merge into develop, while release and hotfix branches merge into main or master. The skill checks whether a develop branch exists locally or remotely and applies these rules automatically.

Does gh pr create work without pushing the branch first?▼

No, the branch must exist on the remote before a pull request can reference it. The skill checks remote branch existence with git ls-remote and runs git push -u origin before creating the PR when needed.

What happens if I have uncommitted changes when creating a PR?▼

The skill detects uncommitted changes via git status and asks whether to commit them first or proceed without committing. This prevents accidentally creating a PR that excludes local modifications.

What are the limitations of automated PR generation with GitHub CLI?▼

The gh CLI must be installed and authenticated beforehand, and PRs cannot be created directly from main or master. If base branch detection is ambiguous, the skill asks the user to confirm rather than guessing.