skills.rest
ksrae
ksraeCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Create GitHub pull requests with conventional-commit titles and descriptions.

Updated Aug 27, 2026
Search Tags:#automation#git#code-review#pull-request#conventional-commits#github-cli#pr-metadata
One-click install
npx skills add https://github.com/ksrae/tag-diary-app --skill create-pr-ksrae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/ksrae/tag-diary-app/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/ksrae/tag-diary-app --skill create-pr-ksrae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull requests often lack consistent titles and descriptive bodies, causing ambiguous reviews and slower merges.

Core Features & Use Cases

  • Conventional-commit driven titles: Generates standardized PR titles from commit messages.
  • Automated PR bodies: Drafts detailed descriptions with linked issues and changelog notes.
  • Workflow guardrails: Verifies prerequisites (gh installed and authenticated, branch ahead of remote) before PR creation.

Quick Start

Create a pull request from your current branch with a conventional-commit based title and a detailed body using the GitHub CLI.

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 using conventional commits?▼

Automating pull request creation uses conventional commit history to generate standardized PR titles and detailed descriptions automatically. It analyzes your Git commits to extract changes, then executes GitHub CLI commands to create the PR with consistent metadata.

What are the prerequisites for generating a PR title and body from Git history?▼

Generating a PR from Git history requires the GitHub CLI to be installed and authenticated. It also verifies that your current branch is ahead of the remote branch before executing the PR creation workflow.

How does conventional commit analysis improve code review workflows?▼

Conventional commit analysis improves code review by enforcing standardized PR messaging. It parses commit messages to draft detailed PR bodies with linked issues and changelog notes, reducing ambiguous reviews and accelerating merges.

Can I use GitHub CLI to draft PR descriptions with linked issues automatically?▼

Yes, you can use GitHub CLI to draft PR descriptions with linked issues automatically. The workflow validates your environment, analyzes Git history for changes, and generates a detailed body with linked issues before executing the creation command.

Why does automated PR generation fail when my branch is not ahead of remote?▼

Automated PR generation fails because workflow guardrails validate that the current branch is ahead of the remote before proceeding. This prevents creating empty pull requests and ensures there are commits to analyze for generating the title and body.

Related Skills

Explore More Software Engineering Skills→
basilisk-labsbasilisk-labs
72

agentplane-task-closure-recovery

Diagnose and resolve Agentplane task synchronization failures with Git and PR states.

Official
Advanced
jobayerarmanjobayerarman

session-ready-for-pr

Prepare a development branch for pull request submission with validation and cleanup.

Community
Intermediate
wildbitcawildbitca
1

github-pr

Enforce conventional commits and standardized PR descriptions in GitHub workflows.

Official
Intermediate
first-flukefirst-fluke
218

create-pr

Create GitHub pull requests from local conventional commits via gh pr create.

Official
Advanced