Create Pull Request

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

You say
Install this skill Read the source first Free Written by n8n-io · unverified publisher
Context cost
1.6k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 6.6 kBtext throughout, nothing executable
Licence
Source-availablefree to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Output format

Produces one artefact, exactly shaped.

developer toolsgithub

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.6 kB · 198 lines
--- name: n8n:create-pr description: 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. allowed-tools: Bash(git:*), Bash(gh:*), Read, Grep, Glob ---
7# Create Pull Request
8
9Creates GitHub PRs with titles that pass n8n's check-pr-title CI validation.
10
11## PR Title Format
12
13```
14<type>(<scope>): <summary>
15```
16
17### Types (required)
18
19| Type | Description | Changelog |
20|------------|--------------------------------------------------|-----------|
21| feat | New feature | Yes |
22| fix | Bug fix | Yes |
23| perf | Performance improvement | Yes |
24| test | Adding/correcting tests | No |
25| docs | Documentation only | No |
26| refactor | Code change (no bug fix or feature) | No |
27| build | Build system or dependencies | No |
28| ci | CI configuration | No |
29| chore | Routine tasks, maintenance | No |
30
31### Scopes (optional but recommended)
32
33- API - Public API changes
34- benchmark - Benchmark CLI changes
35- core - Core/backend/private API
36- editor - Editor UI changes
37- * Node - Specific node (e.g., Slack Node, GitHub Node)
38
39### Summary Rules
40
41- Use imperative present tense: "Add" not "Added"
42- Capitalize first letter
43- No period at the end
44- No ticket IDs (e.g., N8N-1234)
45- Add (no-changelog) suffix to exclude from changelog
46
47## Steps
48
491. **Check current state**:
50 ```bash
51 git status
52 git diff --stat
53 git log origin/master..HEAD --oneline
54 ```
55
562. **Check for implementation plan**: Look for a plan file in .claude/plans/
57 that matches the current branch's ticket ID (e.g. if branch is
58 scdekov/PAY-1234-some-feature, check for .claude/plans/PAY-1234.md).
59 If a plan file exists, ask the user whether they want to include it in the
60 PR description as a collapsible <details> section (see Plan Section below).
61 Only include the plan if the user explicitly approves.
62
633. **If this is a security fix**, audit every public-facing artifact before
64 proceeding (see Security Fixes below).
65
664. **Analyze changes** to determine:
67 - Type: What kind of change is this?
68 - Scope: Which package/area is affected?
69 - Summary: What does the change do?
70
715. **Push branch if needed**:
72 ```bash
73 git push -u origin HEAD
74 ```
75
766. **Create PR** using gh CLI. Read .github/pull_request_template.md as the
77 body structure, then populate each section with actual content before
78 creating the PR:
79 - **Summary**: describe what the PR does
80 - **How to test**: describe how to test the changes. Include an example workflow if appropriate
81 - **Related tickets**: add the Linear ticket URL (https://linear.app/n8n/issue/[TICKET-ID]) and any GitHub issue links
82 - **Checklist**: keep as-is from the template
83 - Add a "🤖 PR Summary generated by AI" at the end of the body
84
85 ```bash
86 gh pr create --draft --title "<type>(<scope>): <summary>" --body "$(cat <<'EOF'
87 <populated body based on pull_request_template.md>
88 EOF
89 )"
90 ```
91
92## PR Body Guidelines
93
94Based on .github/pull_request_template.md:
95
96### Summary Section
97- Describe what the PR does
98- Include screenshots/videos for UI changes
99
100### How to test Section
101- Explain how to test the changes
102- Include an example workflow if appropriate
103
104### Related Links Section
105- Link to Linear ticket: https://linear.app/n8n/issue/[TICKET-ID]
106- Link to GitHub issues using keywords to auto-close:
107 - closes #123 / fixes #123 / resolves #123
108- Link to Community forum posts if applicable
109
110### Checklist
111All items should be addressed before merging:
112- The human author of the PR has checked the "I have seen this code, I have run this code, and I take responsibility for this code." checkbox
113- PR title follows conventions
114- Docs updated or follow-up ticket created
115- Tests included (bugs need regression tests, features need coverage)
116- release/backport label added if urgent fix needs backporting
117
118## Examples
119
120### Feature in editor
121```
122feat(editor): Add workflow performance metrics display
123```
124
125### Bug fix in core
126```
127fix(core): Resolve memory leak in execution engine
128```
129
130### Node-specific change
131```
132fix(Slack Node): Handle rate limiting in message send
133```
134
135### Breaking change (add exclamation mark before colon)
136```
137feat(API)!: Remove deprecated v1 endpoints
138```
139
140### No changelog entry
141```
142refactor(core): Simplify error handling (no-changelog)
143```
144
145### No scope (affects multiple areas)
146```
147chore: Update dependencies to latest versions
148```
149
150## Validation
151
152The PR title must match this pattern:
153```
154^(feat|fix|perf|test|docs|refactor|build|ci|chore|revert)(\([a-zA-Z0-9 ]+( Node)?\))?!?: [A-Z].+[^.]$
155```
156
157Key validation rules:
158- Type must be one of the allowed types
159- Scope is optional but must be in parentheses if present
160- Exclamation mark for breaking changes goes before the colon
161- Summary must start with capital letter
162- Summary must not end with a period
163
164## Plan Section
165
166If a matching plan file was found in .claude/plans/ and the user has approved
167including it, add a collapsible section at the end of the PR body (after the
168checklist, before EOF):
169
170```markdown
171<details>
172<summary>Implementation plan</summary>
173
174<!-- paste plan file contents here -->
175
176</details>
177```
178
179## Security Fixes
180
181**This repo is public.** Never expose the attack vector in any public artifact.
182Describe **what the code does**, not what threat it prevents.
183
184| Artifact | BAD | GOOD |
185|---|---|---|
186| Branch | fix-sql-injection-in-webhook | fix-webhook-input-validation |
187| PR title | fix(core): Prevent SSRF | fix(core): Validate outgoing URLs |
188| Commit msg | fix: prevent denial of service | fix: add payload size validation |
189| PR body | *"attacker could trigger SSRF…"* | *"validates URL protocol and host"* |
190| Linear ref | URL with slug (leaks title) | URL without slug or ticket ID only |
191| Test name | 'should prevent SQL injection' | 'should sanitize query parameters' |
192
193
194**Before pushing a security fix, verify:** no branch name, commit, PR title,
195PR body, Linear URL, test name, or code comment hints at the vulnerability.
196
197**When in doubt, check the Linear issue for possible extra precautions**
198
In the file
SKILL.md960 words
Files1
LicenceSource-available
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,570
on trigger
The instruction body, read only when the skill fires.
0.83%
of a 200k window
Ten skills this size would take about 8% of the window before you open a file.
050k100k150k200k context window

1.6k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 6.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md6.6 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The Source-available licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Create Pull Request · 1.6k tokens when loaded npx mcprush@latest skill add n8n-io/create-pull-request

Writes to .claude/skills/create-pull-request/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencen8n-io/create-pull-request

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0
Claim this skill