skills.rest
mr-phariyawit
mr-phariyawitCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Create GitHub pull requests with validated titles using Bash and gh commands.

Updated Jan 9, 2026
Search Tags:#git#github#validation#pr#ci#pull-request#title-format
One-click install
npx skills add https://github.com/mr-phariyawit/startup --skill create-pr-mr-phariyawit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/mr-phariyawit/startup/tree/main/.agent/skills/create-pr
Command: npx skills add https://github.com/mr-phariyawit/startup --skill create-pr-mr-phariyawit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually formatting PR titles to meet CI checks can slow reviews and cause unnecessary back-and-forth.

Core Features & Use Cases

  • Automatically generate PR titles that conform to the required <type>(<scope>): <summary> format
  • Validate title syntax against allowed types, scopes, and summary guidelines
  • Streamline PR creation in GitHub by integrating with Bash and gh commands

Quick Start

Create a PR with type feat, scope API, and a concise summary.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I format a GitHub PR title to pass check-pr-title CI validation?▼

To pass check-pr-title CI validation, format your GitHub PR title using the <type>(<scope>): <summary> scheme. This ensures your pull request meets the required syntax for allowed types and scopes, preventing CI failures.

What is the correct format for a conventional commit pull request title?▼

A conventional commit pull request title follows the <type>(<scope>): <summary> format. This structure separates the change type, the affected scope, and a concise summary, ensuring the title passes automated CI validation checks.

Can I use the gh CLI to create a PR with a validated title format?▼

Yes, you can use the gh CLI to create a PR with a validated title format. The process integrates Bash and gh commands to automatically generate and validate titles against the required <type>(<scope>): <summary> scheme.

Why does my pull request fail the CI title format check?▼

Your pull request fails the CI title format check because the title does not match the required <type>(<scope>): <summary> scheme. Validating the syntax against allowed types and scopes before submitting resolves the CI validation error.

What are the limitations of automating PR title validation for CI checks?▼

The limitation of automating PR title validation is that it only supports a defined set of types and scopes. If your repository requires custom types outside this defined set, the validation will fail despite the title matching the general <type>(<scope>): <summary> structure.

Related Skills

Explore More Software Engineering Skills→
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
MileniumTickMileniumTick

conventional-commit

Generate XML-structured Conventional Commit messages for Git commits.

Community
Advanced
KemingHeKemingHe
9

pull-merge-request-creation

Generate GitHub and GitLab pull request descriptions from branch diffs and templates.

Community
Intermediate