Agent skill · software engineering · n8n-io
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
Why this skill is useful
Adds a specific workflow for creating GitHub PRs with CI validation that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, git installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Create Pull Request Creates GitHub PRs with titles that pass n8n's check-pr-title CI validation. PR Title Format Types (required) Type Description Changelog ------------ -------------------------------------------------- ----------- feat New feature Yes fix Bug fix Yes perf Performance improvement Yes test Adding/correcting tests No docs Documentation only No refactor Code change (no bug fix or feature) No build Build system or dependencies No ci CI configuration No chore Routine tasks, maintenance No Scopes (optional but recommended) API - Public API changes benchmark - Benchmark CLI changes core - Core/backend/private API editor - Editor UI changes engine - New workflow execution engine v2 (@n8n/engine package) Node - Specific node (e.g., Slack Node, GitHub Node) Summary Rules Use imperative present tense: "Add" not "Added" Capitalize first letter No period at the end No ticket IDs (e.g., N8N-1234) Add (no-changelog) suffix to exclude from changelog Steps 1. Check current state: 2. Check for implementation plan: Look for a plan file in the repository plan directories (.claude/plans/ or .agents/plans/ when present) that matches the current branch's ticket ID (e.g. if branch is scdekov/PAY-1234-some-feature, check for PAY-1234.md). If a plan file exists, ask the user whether they want to include it in the PR description as a collapsible <details> section (see Plan Section below). Only include the plan if the user explicitly approves. 3. If this is a security fix, audit every public-facing artifact before proceeding (see Security Fixes below). 4. Analyze changes to determine: Type: What kind of change is this? Scope: Which package/area is affected? Summary: What does the change do? 5. Push branch if needed: 6. Create PR using gh CLI. Read .github/pullrequesttemplate.md as the body structure, then populate each section with actual content before creating the PR: Summary: describe what the PR does How to test: describe how to test the changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/create-pr