pr-create

Generate a complete pull request body and open it via gh pr create.

5|3|Updated Jun 18, 2024
One-click install
npx skills add https://github.com/Unique-AG/ai --skill pr-create-unique-ag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/Unique-AG/ai/tree/main/.claude/skills/pr-create
Command: npx skills add https://github.com/Unique-AG/ai --skill pr-create-unique-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs are often created with inconsistent titles, missing refs, and incomplete bodies. This skill automates end-to-end PR authoring by inferring a semantic title, extracting issue references from branch names and commits, and composing a complete PR body for creation via gh pr create.

Core Features & Use Cases

  • Auto-draft a semantic PR title from branch name, commit history, and diff intent.
  • Auto-extract issue references from branch names and commits (Jira, GitHub issues, and common patterns).
  • Auto-generate a complete PR body with summary, grouped changes, test plan, and risk/rollout notes.
  • Ask for confirmation only (or when missing issue refs) before creating the PR.
  • Create the PR with gh pr create after explicit user approval.
  • Supporting file: assets/pr-description.template

Quick Start

Draft and open a PR from your current git context by inferring a semantic title, extracting refs, and generating a complete body for review, then await your explicit approval to create the PR.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I automatically generate a pull request title and body from git commits?

You can automatically generate a pull request title and body from git commits using this skill, which infers a semantic title from your branch name and commit history, then composes a complete PR body with grouped changes and test plans for review.

How do I extract issue references from a git branch name for a pull request?

To extract issue references from a git branch name for a pull request, this skill automatically scans your branch names and commit history for Jira and GitHub issue patterns, prompting you when references are missing before creating the PR.

Can I use gh pr create to open a pull request after reviewing an auto-generated draft?

Yes, you can use gh pr create to open a pull request after reviewing an auto-generated draft, as this skill awaits your explicit approval before executing the command to ensure you maintain full control over the creation process.

Does this pull request automation tool work without linking a Jira or GitHub issue?

This pull request automation tool works without linking a Jira or GitHub issue, but it will prompt you for the missing issue references to ensure PR traceability and consistency before you approve the PR creation.

What is the best way to ensure consistent PR descriptions across a development team?

The best way to ensure consistent PR descriptions across a development team is to automate end-to-end PR authoring, which standardizes the PR body with a summary, grouped changes, test plan, and risk notes based on your git context.