skills.rest
exposir
exposirCOMMUNITY
Explore all skills by this author →
𝕏@ExposirMGitHub

create-pr

Create GitHub pull requests with formatted titles using the GitHub CLI.

Updated Aug 23, 2026
Search Tags:#git#pr#gh#ci#pull-request#title-formatting
One-click install
npx skills add https://github.com/exposir/ai-talk --skill create-pr-exposir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/exposir/ai-talk/tree/main/notes/skill/create-pr
Command: npx skills add https://github.com/exposir/ai-talk --skill create-pr-exposir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate GitHub PR titles that conform to the check-pr-title CI rules, reducing manual formatting errors and review overhead.

Core Features & Use Cases

  • Enforces PR title format: <type>(<scope>): <summary> to ensure consistency across PRs.
  • Guides scope usage for common areas like API, core, editor, and Node changes.
  • Speeds up PR creation by ensuring compliance with PR title conventions during PR creation.

Quick Start

Create a PR with a correctly formatted title that passes the check-pr-title CI validation.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a GitHub PR with a properly formatted title?▼

To create a GitHub PR with a properly formatted title, this automation enforces the <type>(<scope>): <summary> convention and uses the GitHub CLI to execute the pull request creation automatically.

What is the correct format for a GitHub PR title to pass CI checks?▼

The correct PR title format to pass CI checks is <type>(<scope>): <summary>, which ensures consistency across pull requests and reduces manual formatting errors during code review.

How do I automate GitHub pull request creation using the gh CLI?▼

You can automate GitHub pull request creation by leveraging the gh CLI to generate PRs while applying documented type and scope formatting conventions, reducing manual overhead and review friction.

What scopes should I use when formatting my pull request titles?▼

Common scopes for formatting pull request titles include API, core, editor, and Node, guiding developers to accurately categorize changes within the <type>(<scope>): <summary> structure.

Why do my GitHub PR titles fail the check-pr-title CI validation?▼

PR titles fail the check-pr-title CI validation when they do not conform to the required <type>(<scope>): <summary> format, a problem this automation solves by enforcing conventions during creation.

Can I use this PR creation automation for submitting code changes for review?▼

Yes, you can use this PR creation automation for submitting code changes for review, as it triggers when a user requests a pull request or says /pr, ensuring compliant titles.

Related Skills

Explore More Software Engineering Skills→
QuintenpsQuintenps

git-workflow

Standardize version control operations with a three-branch model and git worktrees.

Community
Advanced
WesleyMFrederickWesleyMFrederick

merging-feature-branches-to-main

Squashes Git feature-branch history into a single commit when merging to main.

Community
Basic
nicolanoviellnicolanoviell
2

code-review

Review code changes for bugs, style issues, and best practices.

Community
Intermediate
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate