skills.rest
landmaster135
landmaster135COMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-pr

Create GitHub pull requests with conventional title format.

Updated Apr 9, 2025
Search Tags:#automation#git#github#pr#pull-request#checks#title-format
One-click install
npx skills add https://github.com/landmaster135/devbox --skill create-pr-landmaster135
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/landmaster135/devbox/tree/main/.config/codex/skills/project-documentation/commands/pull-request-creator-origin
Command: npx skills add https://github.com/landmaster135/devbox --skill create-pr-landmaster135

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating GitHub pull requests with consistently formatted titles is error-prone and brittle, leading to failed CI checks and review delays. This skill enforces a standard PR title format so contributions are predictable and compliant.

Core Features & Use Cases

  • Enforces PR title format according to the conventional <type>(<scope>): <summary> pattern.
  • Provides guidance for PR bodies that align with project contribution standards.
  • Supports common types (feat, fix, perf, docs, refactor, etc.) and optional scopes to improve traceability.

Quick Start

Create a pull request with a title following the required format and a descriptive body.

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 pull request title to pass CI checks?▼

To format a GitHub pull request title to pass CI checks, use the conventional <type>(<scope>): <summary> pattern. This standardizes contributions, ensuring titles are predictable and compliant with automated validation rules.

What is the conventional PR title format for collaborative software development?▼

The conventional PR title format for collaborative software development follows the <type>(<scope>): <summary> pattern. Common types include feat, fix, perf, docs, and refactor, with optional scopes to improve traceability and review speed.

Why does my pull request fail automation checks?▼

Your pull request might fail automation checks because the title does not adhere to the required <type>(<scope>): <summary> format. Enforcing standard PR title formatting prevents brittle contributions and eliminates CI validation failures.

How do I create a GitHub pull request with a compliant body?▼

To create a GitHub pull request with a compliant body, follow the required title format and provide a descriptive body that aligns with your project's contribution standards, ensuring consistent and review-friendly contributions.

Do I need to specify a scope for every pull request type?▼

No, you do not need to specify a scope for every pull request type. Scopes are optional in the conventional PR title format, but using them with types like feat or fix can improve traceability in collaborative software development workflows.

Related Skills

Explore More Software Engineering Skills→
mathiasbourgoinmathiasbourgoin
2

git-conventions

Standardize git commit messages, branch names, and pull request descriptions.

Community
Intermediate
nashgaonashgao
3

Merge Pull Request Command

Merge pull requests into a target branch with validation and quality gates.

Community
Advanced
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
x402agentx402agent

create-github-pr

Automate GitHub pull request creation with the gh CLI.

Community
Intermediate