skills.rest
n8n-io
n8n-ioOFFICIAL
Explore all skills by this author →
Website𝕏@n8n_ioGitHub

create-pr

Create GitHub pull requests with compliant type(scope): summary titles via CLI or API.

200k|60.0k|Updated Jun 22, 2019
Search Tags:#pull request#GitHub#CI#gh CLI#check-pr-title#title formatting
One-click install
npx skills add https://github.com/n8n-io/n8n --skill create-pr-n8n-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/n8n-io/n8n/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/n8n-io/n8n --skill create-pr-n8n-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures GitHub pull requests are created with properly formatted titles that pass the check-pr-title CI validation, reducing manual review time and back-and-forth.

Core Features & Use Cases

  • Enforced title format: Generate PR titles using the conventional type(scope): summary pattern to align with project conventions.
  • Streamlined collaboration: Quickly submit changes for review when teammates ask for a PR or when you use /pr.
  • Use Case: Example: you implemented a bug fix in core and want to open a PR with a title like fix(core): Resolve nil pointer in user session management.

Quick Start

Create a PR with a properly formatted title using gh pr create or your preferred GitHub API.

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 the check-pr-title CI validation?▼

To pass the check-pr-title CI validation, format your GitHub PR title using the type(scope): summary pattern. This skill enforces this conventional structure, supporting common scopes to ensure your pull request titles align with project requirements.

How do I create a GitHub pull request using the gh CLI with a compliant title?▼

You can create a GitHub pull request with a compliant title by using the gh pr create command or GitHub API integrations. This skill automatically formats the title using the type(scope): summary pattern before submission.

What title format is required for GitHub pull requests to pass CI checks?▼

The required title format for GitHub pull requests to pass CI checks is type(scope): summary. This pattern enforces conventional commits structure, utilizing common scopes to categorize changes like bug fixes or feature additions.

Can I use this skill to open a PR when a teammate asks for /pr during a code review?▼

Yes, you can use this skill to open a PR when a teammate asks for /pr during a code review. It streamlines collaboration by automatically generating a properly formatted type(scope): summary title and submitting it via the GitHub CLI.

Why does my GitHub pull request fail the check-pr-title CI validation?▼

Your GitHub pull request fails the check-pr-title CI validation because the title does not match the required type(scope): summary pattern. This skill enforces that specific formatting structure to prevent CI failures and reduce manual review back-and-forth.

Related Skills

Explore More Software Engineering Skills→
shirulotshirulot

yeet

Automate Git staging, committing, and GitHub pull request creation.

Community
Advanced
dsifrydsifry
7

pr-shepherd

Monitor GitHub pull requests and resolve CI failures until merge.

Community
Advanced
Taketo-YodaTaketo-Yoda
4

commit

Create conventional commits with pre-flight formatting, linting, and secret checks.

Community
Advanced
kivo360kivo360
71

PR Creator

Generate standardized pull request titles, descriptions, and labels from templates.

Community
Basic