skills.rest
first-fluke
first-flukeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-pr

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

218|33|Updated Jan 7, 2026
Search Tags:#automation#pr#GitHub CLI#pull-request#conventional-commits#title-generation#body-generation
One-click install
npx skills add https://github.com/first-fluke/fullstack-starter --skill create-pr-first-fluke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/first-fluke/fullstack-starter/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/first-fluke/fullstack-starter --skill create-pr-first-fluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub Pull Requests from your local commits, ensuring consistent titles and descriptions derived from conventional commits, which saves time and reduces manual PR drafting errors.

Core Features & Use Cases

  • Conventional-commit driven PRs: Generates standardized titles and bodies from your commit messages.
  • Automated PR publishing: Uses gh pr create to open PRs from the current branch with minimal interaction.
  • Workflow-friendly: Suitable for local dev workflows or CI/CD pipelines that require predictable PR metadata.

Quick Start

Create a PR for the current branch using conventional commits: gh pr create --title "feat: ..." --body "..."

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

You can automate pull request creation by parsing local conventional commits to generate standardized PR titles and bodies, then using the GitHub CLI to publish the PR from your current branch with minimal manual interaction.

How does conventional commit parsing generate PR titles and bodies?▼

Conventional commit parsing extracts structured data from your local commit messages to compose predictable PR metadata, automatically generating standardized titles and bodies that streamline your PR workflow.

Can I use GitHub CLI to open pull requests in a CI/CD pipeline?▼

Yes, the GitHub CLI supports automated PR publishing suitable for CI/CD pipelines, generating predictable PR metadata from conventional commits to open PRs with minimal required interaction.

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

Generating PR titles from conventional commit messages ensures consistency across your development team, reducing manual drafting errors by standardizing the PR creation workflow through automated commit parsing.

Do I need GitHub CLI installed to automate PR creation from local commits?▼

Yes, you need the GitHub CLI installed and access to the target repository to execute gh pr create and publish pull requests generated from your local conventional commits.

Why does automated PR creation require access to the repository?▼

Automated PR creation requires repository access because the GitHub CLI must authenticate with your repository to publish branches and submit the generated pull request metadata successfully.

Related Skills

Explore More Software Engineering Skills→
amanning3390amanning3390
13

github-workflow

Automate GitHub repository, branch, PR, issue, and release workflows via gh CLI.

Community
Intermediate
mkalkeremkalkere
4

pr-complete

Verify GitHub PR readiness by checking approvals, CI status, mergeability, and notify humans via bus message.

Community
Advanced
GolferGeekGolferGeek

Orchestrator Git Standards

Enforce conventional branch names, commit messages, and repository organization for Git workflows.

Community
Basic
paultyngpaultyng
9

ship-it

Automate Git pre-commit checks, changelog generation, and GitHub pull request updates.

Community
Advanced