create-pr

Creates GitHub pull requests with titles that pass n8n's check-pr-title CI validation.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Uguryldz/n8nclean --skill create-pr-uguryldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Uguryldz/n8nclean/tree/main/.claude/plugins/n8n/skills/create-pr
Command: npx skills add https://github.com/Uguryldz/n8nclean --skill create-pr-uguryldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating pull requests in the n8n repository requires strict adherence to the check-pr-title CI validation rules, and malformed titles or incomplete PR bodies cause CI failures and review delays. ## Core Features & Use Cases - Conventional PR Titles: Generates titles in the type(scope): summary format with correct types, scopes, capitalization, and breaking-change markers. - Structured PR Bodies: Builds PR descriptions from the repository template including summary, related Linear tickets and GitHub issues, and the review checklist. - Security Fix Sanitization: Audits branch names, commits, titles, and test names so security fixes never expose the attack vector in public artifacts. - Use Case: After committing a bug fix on a feature branch, ask for a PR and receive a draft pull request with a validated title like fix(core): Resolve memory leak in execution engine, a complete body, and an optional collapsible implementation plan section. ## Quick Start Ask the assistant to create a pull request for the current branch and it will analyze the changes, format a compliant title, and open a draft PR using the gh CLI.

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 pull request that passes n8n's check-pr-title validation?▼

Use the format type(scope): summary, where type is one of feat, fix, perf, test, docs, refactor, build, ci, or chore. The summary must start with a capital letter, use imperative present tense, and not end with a period.

What PR title format does the n8n repository require?▼

Titles must match the pattern type(optional scope): summary, validated by a regex in CI. Scopes include API, core, editor, benchmark, or a specific node name like Slack Node, and breaking changes add an exclamation mark before the colon.

How do I exclude a pull request from the n8n changelog?▼

Add the (no-changelog) suffix to the PR title summary, for example refactor(core): Simplify error handling (no-changelog). Types like docs, test, refactor, build, ci, and chore are already excluded from the changelog by default.

How should security fixes be described in public pull requests?▼

Describe what the code does, never the threat it prevents, since the repository is public. Use neutral branch names, titles, commit messages, and test names such as fix(core): Validate outgoing URLs instead of mentioning SSRF or injection.

Can the PR body include the implementation plan from .claude/plans?▼

Yes, if a plan file matching the branch's ticket ID exists, the skill asks whether to include it. Only with explicit approval is the plan appended as a collapsible details section at the end of the PR body.