skills.rest
opmau
opmauCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Analyze commits and generate a structured pull request with approval gating.

6|Updated Feb 7, 2026
Search Tags:#automation#git#workflow#branch#pr#code-review#pull-request
One-click install
npx skills add https://github.com/opmau/claude-code-framework --skill create-pr-opmau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/opmau/claude-code-framework/tree/main/templates/.claude/skills/create-pr
Command: npx skills add https://github.com/opmau/claude-code-framework --skill create-pr-opmau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating consistent, well-described pull requests from your working branch to streamline reviews and reduce back-and-forth.

Core Features & Use Cases

  • Analyze all commits on the current branch to capture the full scope of changes.
  • Generate a conventional, concise PR title and a structured body with a Summary, Changes, and Test Plan.
  • Push changes and create the PR with upstream tracking after your explicit approval.

Quick Start

Invoke the create-pr skill on your current branch and approve the generated PR description when prompted.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from my current git branch?▼

Automating pull request creation from your git branch involves analyzing all commits to generate a concise conventional title and a structured body with a Summary, Changes, and Test Plan. The workflow then pushes with upstream tracking and creates the PR after your explicit approval.

What is the best way to generate a structured PR description with a summary and test plan?▼

Generating a structured PR description with a summary and test plan requires analyzing all branch commits to capture the full scope of changes. This approach produces consistent, multi-section metadata including a Summary, Changes, and Test Plan to streamline reviews and reduce back-and-forth.

Can I select a base branch and require approval before pushing changes for code review?▼

Yes, you can select a base branch and require explicit approval before pushing changes. This workflow applies base-branch selection and approval gating, ensuring the push with upstream tracking and subsequent PR creation only happens after you review and approve the generated description.

Do I need to manually write commit messages for consistent pull request metadata across teams?▼

No, you do not need to manually write commit messages for consistent pull request metadata. The workflow analyzes all commits on your branch automatically to capture the full scope of changes and generates consistent PR metadata needed across multiple commits and teams.

How to handle upstream tracking when pushing a branch to create a pull request?▼

Handling upstream tracking when pushing a branch to create a pull request is done automatically. After analyzing commits, generating the PR title and body, and receiving your explicit approval, the workflow pushes your changes with upstream tracking enabled to finalize the PR creation.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

Git Sync

Fetches Git remote changes and displays local branch status vs upstream tracking branch.

Community
Intermediate
louisfghbvclouisfghbvc
4

ship

Automate the end-to-end ship workflow from base branch detection to PR creation.

Community
Advanced
kangmominkangmomin
1

commit-pr-hd

Automate commit, branch creation, and pull request workflows on repositories.

Community
Advanced
hadenlabshadenlabs
1

github-create-pr

Create a GitHub pull request from the current branch with generated metadata.

Official
Advanced