n8n create-pr：自动化创建符合规范的GitHub拉取请求标题与PR

create-pr by n8n-io/n8n

676 周安装量

180,900 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/n8n-io/n8n --skill create-pr

开发自动化开发运维

🇨🇳中文介绍

创建拉取请求

创建符合 n8n check-pr-title CI 验证规则的 GitHub PR 标题。

PR 标题格式

<type>(<scope>): <summary>

类型（必需）

类型	描述	更新日志
`feat`	新功能	是
`fix`	错误修复	是
`perf`	性能改进	是

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

FlyClaw：零登录航班聚合查询工具，Python实现多源航班信息与价格搜索

4,000,000 周安装

find-skills 技能搜索工具 - Vercel Labs 开源智能体技能包管理器

749,400 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

255,700 周安装

Vercel Web界面规范检查工具 - 自动检测代码是否符合Web设计指南

205,600 周安装

API - 公共 API 变更
benchmark - Benchmark CLI 变更
core - 核心/后端/私有 API
editor - 编辑器 UI 变更
* Node - 特定节点（例如 Slack Node、GitHub Node）

检查当前状态：

git status git diff --stat git log origin/master..HEAD --oneline
分析变更以确定：
- 类型：这是什么类型的变更？
- 作用域：哪个包/区域受到影响？
- 摘要：这个变更做了什么？
推送分支（如果需要）：

git push -u origin HEAD
创建 PR 使用 gh CLI 并应用 .github/pull_request_template.md 中的模板：

gh pr create --draft --title "<type>(<scope>): <summary>" --body "$(cat <<'EOF' ## 摘要

## 相关的 Linear 工单、GitHub 问题和社区论坛帖子

<!-- 链接到 Linear 工单：https://linear.app/n8n/issue/[TICKET-ID] -->
<!-- 使用 "closes #<issue-number>"、"fixes #<issue-number>" 或 "resolves #<issue-number>" 来自动关闭问题 -->

## 审查/合并清单

- [ ] PR 标题和摘要具有描述性。（[规范](../blob/master/.github/pull_request_title_conventions.md)）
- [ ] [文档已更新](https://github.com/n8n-io/n8n-docs) 或已创建跟进工单。
- [ ] 包含测试。
- [ ] PR 已标记 `release/backport`（如果 PR 是需要回退的紧急修复）
EOF
)"

链接到 Linear 工单：https://linear.app/n8n/issue/[TICKET-ID]
使用关键词链接到 GitHub 问题以自动关闭：
- closes #123 / fixes #123 / resolves #123
如果适用，链接到社区论坛帖子

🇺🇸English

Create Pull Request

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

PR Title Format

<type>(<scope>): <summary>

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
* 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

Check current state :

git status git diff --stat git log origin/master..HEAD --oneline
Analyze changes to determine:
- Type: What kind of change is this?
- Scope: Which package/area is affected?
- Summary: What does the change do?
Push branch if needed :

git push -u origin HEAD
Create PR using gh CLI with the template from .github/pull_request_template.md:

gh pr create --draft --title "<type>(<scope>): <summary>" --body "$(cat <<'EOF' ## Summary

<Describe what the PR does and how to test. Photos and videos are recommended.>

## Related Linear tickets, Github issues, and Community forum posts

<!-- Link to Linear ticket: https://linear.app/n8n/issue/[TICKET-ID] -->
<!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues -->

## Review / Merge checklist

- [ ] PR title and summary are descriptive. ([conventions](../blob/master/.github/pull_request_title_conventions.md))
- [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up ticket created.
- [ ] Tests included.
- [ ] PR Labeled with `release/backport` (if the PR is an urgent fix that needs to be backported)
EOF
)"

PR Body Guidelines

Based on .github/pull_request_template.md:

Summary Section

Describe what the PR does
Explain how to test the changes
Include screenshots/videos for UI changes

Checklist

All items should be addressed before merging:

PR title follows conventions
Docs updated or follow-up ticket created
Tests included (bugs need regression tests, features need coverage)
release/backport label added if urgent fix needs backporting

Examples

Feature in editor

feat(editor): Add workflow performance metrics display

Bug fix in core

fix(core): Resolve memory leak in execution engine

Node-specific change

fix(Slack Node): Handle rate limiting in message send

Breaking change (add exclamation mark before colon)

feat(API)!: Remove deprecated v1 endpoints

No changelog entry

refactor(core): Simplify error handling (no-changelog)

No scope (affects multiple areas)

chore: Update dependencies to latest versions

Validation

The PR title must match this pattern:

^(feat|fix|perf|test|docs|refactor|build|ci|chore|revert)(\([a-zA-Z0-9 ]+( Node)?\))?!?: [A-Z].+[^.]$

Key validation rules:

Type must be one of the allowed types
Scope is optional but must be in parentheses if present
Exclamation mark for breaking changes goes before the colon
Summary must start with capital letter
Summary must not end with a period

Weekly Installs

661

Repository

n8n-io/n8n

GitHub Stars

180.7K

First Seen

Jan 20, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode507

claude-code487

gemini-cli486

codex458

cursor436

github-copilot408

n8n create-pr：自动化创建符合规范的GitHub拉取请求标题与PR

🇨🇳中文介绍

创建拉取请求

PR 标题格式

类型（必需）

相关 Skills

作用域（可选但推荐）

摘要规则

步骤

PR 正文指南

摘要部分

相关链接部分

清单

示例

编辑器中的功能

核心中的错误修复

特定节点变更

破坏性变更（在冒号前添加感叹号）

不包含在更新日志中

无作用域（影响多个区域）

验证