skills.rest
IITApurba
IITApurbaCOMMUNITY
Explore all skills by this author →
GitHub

Create Pull Request

Create GitHub pull requests with compliant titles and structured metadata.

Updated May 6, 2026
Search Tags:#automation#git#pull request#github#pr#ci#check-pr-title
One-click install
npx skills add https://github.com/IITApurba/Distributed-Workflow-Execution-Engine --skill create-pull-request-iitapurba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Create Pull Request
Source: https://github.com/IITApurba/Distributed-Workflow-Execution-Engine/tree/main/.claude/plugins/n8n/skills/create-pr
Command: npx skills add https://github.com/IITApurba/Distributed-Workflow-Execution-Engine --skill create-pull-request-iitapurba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you create GitHub pull requests with titles that pass the repository's check-pr-title CI validation, reducing back-and-forth and speeding up reviews.

Core Features & Use Cases

  • Enforces the <type>(<scope>): <summary> PR title format
  • Integrates with GitHub via gh CLI to create PRs and manage metadata
  • Useful when user asks to create a PR (or says /pr) or when submitting changes for review.

Quick Start

Ask me to create a GitHub pull request with a properly formatted title.

Frequently Asked Questions about Create Pull Request

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

FAQPage Schema
How do I create a GitHub pull request that passes check-pr-title CI validation?▼

To create a GitHub pull request that passes check-pr-title CI validation, you must format the title as <type>(<scope>): <summary>. This automation enforces that structure and uses the gh CLI to submit the PR with compliant metadata.

What is the required format for GitHub PR titles to pass CI checks?▼

The required format for GitHub PR titles to pass CI checks is <type>(<scope>): <summary>. This ensures the title correctly parses the type and scope, satisfying explicit CI validation requirements before review.

How do I automate pull request creation with structured metadata using gh?▼

You can automate pull request creation with structured metadata using gh by triggering the process via a /pr request. The automation leverages gh and git commands to format titles and submit changes for review across software projects.

Does this PR creation automation require manual title formatting?▼

No, this PR creation automation does not require manual title formatting. It automatically enforces the <type>(<scope>): <summary> format and handles type/scope parsing to ensure titles pass CI checks without manual intervention.

Why does my pull request fail CI validation when submitting changes for review?▼

Your pull request fails CI validation when submitting changes for review if the title lacks the correct <type>(<scope>): <summary> format. This automation prevents those failures by structuring metadata to satisfy explicit CI check requirements.

Related Skills

Explore More Software Engineering Skills→
TugoukezhangTugoukezhang
8

github

Execute gh CLI commands to manage GitHub issues, PRs, runs, and API queries.

Community
Intermediate
x-TheFoxx-TheFox

github-pr-workflow

Automate GitHub PR lifecycle from branch creation to merge.

Community
Advanced
Room-CRoom-C

rc:commit

Stage, format, and push git changes with conventional commits.

Official
Intermediate
boundless-xyzboundless-xyz
195

pr

Create or update a GitHub pull request for current git changes.

Official
Intermediate