skills.rest
Noyoucringe
NoyoucringeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-pr

Create GitHub pull requests with titles matching check-pr-title CI validation.

Updated Mar 20, 2026
Search Tags:#git#github#pr#code-review#pull-request#title-formatting#ci-checks
One-click install
npx skills add https://github.com/Noyoucringe/n8n-workflow --skill create-pr-noyoucringe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Noyoucringe/n8n-workflow/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/Noyoucringe/n8n-workflow --skill create-pr-noyoucringe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation.

Core Features & Use Cases

  • Enforces PR title format (type(scope): summary) for consistency
  • Supports common types (feat, fix, docs, perf, etc.) and optional scopes
  • Triggers PR creation via user prompts (e.g., /pr) across repositories

Quick Start

Create a GitHub pull request with a properly formatted title that follows the repository's conventions.

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 pull request with a title that passes CI validation?▼

To create a GitHub pull request with a title that passes CI validation, use this skill to automatically enforce the type(scope): summary format. It ensures your PR titles align with the required check-pr-title conventions for predictable changelog generation.

What is the correct format for a GitHub PR title to pass check-pr-title checks?▼

The correct format for a GitHub PR title to pass check-pr-title checks is type(scope): summary. This skill enforces allowed types like feat, fix, docs, or perf, along with optional scopes, ensuring your title meets the repository's formatting conventions.

Can I automate pull request creation across multiple repositories?▼

Yes, you can automate pull request creation across multiple repositories by triggering this skill with user prompts like /pr. It consistently applies the allowed types, scopes, and summary formats defined in the skill metadata to ensure predictable PRs.

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

Your pull request likely fails check-pr-title CI validation because the title does not follow the required type(scope): summary format. This skill automatically formats your PR title with allowed types like feat or fix to ensure it passes the validation.

Do I need to manually specify the scope when formatting a pull request title?▼

No, you do not need to manually specify the scope when formatting a pull request title if it is optional for your repository. This skill enforces the allowed types and summary formats while supporting optional scopes defined in the metadata.

Related Skills

Explore More Software Engineering Skills→
jobayerarmanjobayerarman

session-ready-for-pr

Prepare a development branch for pull request submission with validation and cleanup.

Community
Intermediate
Avishai-TsabariAvishai-Tsabari

release

Coordinate Paperclip release operations across changelog, verification, publishing, and announcements.

Community
Advanced
Pixel-Process-UGPixel-Process-UG
1

git-commit-helper

Analyze staged diffs and generate conventional commit messages.

Official
Intermediate
windmill-labswindmill-labs
17.5k

pr

Create draft GitHub pull requests with conventional commit titles.

Official
Advanced