CR

Automates PR creation with valid formatting for CI check compliance.

Install

mkdir -p .claude/skills/create-pr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/549" && unzip -o skill.zip -d .claude/skills/create-pr && rm skill.zip

Installs to .claude/skills/create-pr

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
217 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • →Formats PR titles to pass CI validation
  • →Generates PR body from repository templates
  • →Includes implementation plans from repository directories
  • →Automates branch pushing and PR creation
  • →Enforces security-conscious artifact naming

How it works

The agent analyzes local git changes to determine the PR type and scope, then uses the GitHub CLI to create a pull request populated with content from the repository's template.

Inputs & outputs

You give it
Code changes on a feature branch
You get back
A GitHub pull request with a validated title and populated body

When to use create-pr

  • →Submit a pull request for a fix
  • →Create a PR with a formatted title
  • →Prepare a feature branch for review

About this skill

Create Pull Request

Creates GitHub PRs with titles that pass n8n's check-pr-title CI validation and short descriptions that tell the reviewer what the diff does not show.

PR Title Format

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

Types (required)

TypeDescriptionChangelog
featNew featureYes
fixBug fixYes
perfPerformance improvementYes
testAdding/correcting testsNo
docsDocumentation onlyNo
refactorCode change (no bug fix or feature)No
buildBuild system or dependenciesNo
ciCI configurationNo
choreRoutine tasks, maintenanceNo

Scopes (optional but recommended)

  • API - Public API changes
  • ai-builder - AI Workflow Builder and Instance AI
  • benchmark - Benchmark CLI changes
  • core - Core/backend/private API
  • editor - Editor UI changes
  • engine - New workflow execution engine v2 (@n8n/engine package & engine-v2 module in cli)
  • * Node - Specific node (e.g., Slack Node, GitHub Node)

check-pr-title accepts only these scopes. Do not use a package or folder name as the scope (for example instance-ai, cli, evals or docker). If no scope fits, omit the scope. To give two scopes, separate them with a comma and a space: fix(core, editor): ....

Title Summary Rules

  • Use imperative present tense: "Add" not "Added"
  • Capitalize first letter
  • No period at the end
  • No ticket IDs (e.g., N8N-1234) and no PR numbers (e.g., #12345)
  • Add (no-changelog) as the last part to exclude the PR from the changelog, unless the type already excludes it
  • Put the exclamation mark for a breaking change before the colon

Steps

  1. Check current state:

    git status
    git diff --stat
    git log origin/master..HEAD --oneline
    
  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 scope from the Scopes list fits? Omit the scope if none fits.
    • Title summary: What does the change do?
    • Insights: What did the session (debugging, measurements, user discussion) find that a reviewer would otherwise miss?
  5. Identify feature flag test settings: Inspect the full PR diff for new PostHog flags. Record the keys and values needed to test the new behavior as described in Feature Flag Test Settings below.

  6. Push branch if needed:

    git push -u origin HEAD
    
  7. Create PR using gh CLI. Read .github/pull_request_template.md as the body structure, then populate each section with actual content before creating the PR:

    • Summary: what the PR does and why, plus any surprises (see PR Body Guidelines below)
    • How to test: the steps that a person follows in the product to see the change work, and the command that runs the tests
    • Related tickets: add the Linear ticket URL (https://linear.app/n8n/issue/[TICKET-ID]), any GitHub issue links, and the docs link if there is one

    Before you create the PR, proofread the Summary against the Summary Section rules. Delete each sentence that restates the diff, or that is not the what-and-where sentence, the why, or a surprise. Make sure that each sentence is true for the diff.

    When a later commit changes a fact in the body, update the body.

    gh pr create --draft --title "<type>(<scope>): <summary>" --body "$(cat <<'EOF'
    <populated body based on pull_request_template.md>
    EOF
    )"
    

Feature Flag Test Settings

  1. Compare the branch with origin/master using git diff origin/master...HEAD. If the PR targets another branch, use origin/<target-branch> instead. Inspect new experiment definitions in packages/frontend/editor-ui/src/app/constants/experiments.ts, shared flag constants in packages/@n8n/api-types, and new PostHog checks elsewhere in the diff. Resolve constants to the exact PostHog key string. Exclude removed flags, existing flags that the PR only references, and flag names that appear only in tests or documentation.
  2. Select a test value for each new flag. Use true to enable a boolean flag. Read the flag's consumers and variant definitions for an A/B experiment. Use the exact variant that shows the new behavior. Do not assume that boolean true selects a named variant. If the required variant is unclear, report it instead of guessing. Preserve any value that the user explicitly requested for the same key.
  3. If step 1 found at least one new flag, include N8N_FEATURE_FLAG_OVERRIDES in How to test. This environment variable accepts a JSON object that maps PostHog keys to boolean values or named variants. Tell the tester to set it before starting the test instance. For example:
    export N8N_FEATURE_FLAG_OVERRIDES='{"136_skill_sync":true}'
    
    Use JSON false to disable a boolean flag, or a string for a named variant. Combine multiple overrides in one JSON object.

The Codespace preview runner does not read flag: labels. Do not create or apply them. For supported preview settings, see the Preview toggles and Preview environment from a webhook sections in .github/WORKFLOWS.md.

PR Body Guidelines

Based on .github/pull_request_template.md.

Keep the description short. The reviewer reads the diff for the details. The description gives only what the diff cannot show: why the change exists, and what could surprise the reviewer. Keep the length in proportion to the complexity of the change: a complex change usually has more surprises. A change with no surprises needs only the first two paragraphs of the Summary.

Write for an engineer. Use exact technical terms, and do not simplify them. Use ASD-STE100 Simplified Technical English: short sentences, active voice, plain technical verbs, no metaphors.

Summary Section

Write the Summary as up to three paragraphs:

<Verb> <what> in <area>.

<Why: the product value or the problem, and the rationale for the main choices.>

<Important details, only if there are surprises.>
  1. What and where: one sentence in the imperative mood, like the PR title ("Fix the ...", "Add ...", "Change the ..."). Do not start with "This PR". State the area of the product or code (for example, a node, the editor, or the CI pipeline) and the nature of the change, for example a bug fix or a feature. Do not name functions or fields. The diff shows them.
  2. Why: one or two sentences: the product value that the change adds or the problem that it fixes, and the rationale for the main choices.
  3. Important details: add this paragraph only when the change has one of these surprises. Give each surprise one or two sentences:
    • Unexpected behaviour: a change in behaviour for users or for other code paths, a changed default, a migration, or a side effect outside the obvious scope.
    • Technical challenge: a root cause that is not obvious, a constraint that forced the design, a workaround, or a known gap or follow-up.
    • Rejected alternative: only when a reviewer would suggest it. Give one sentence with the concrete reason it fails.
    • Insight from the work: a surprising fact that you found while you made the change and that the diff and the ticket do not show. For example, a measurement, a reproduction detail, a cause found while debugging, or an error in the ticket.

Leave out what the diff shows: file lists, renamed fields, call order, test names, error cases, and descriptions of the code. Leave out framework behaviour that reviewers know. Do not add background or a closing sentence. Define an n8n-internal term only if an engineer from another team would not know it. For UI changes, add screenshots or videos in a | Before | After | table.

How to test Section

  • Write short steps for a person who tests the product change by hand: the setup, the action in the n8n UI or API, and the expected result
  • Add an example workflow only if the test needs one
  • If the change needs a non-default module (N8N_ENABLED_MODULES), an enterprise license, a feature flag, or similar, give the setting
  • If nothing changes for a user, write one short line that starts with "No visible changes", for example "No visible changes, only tests." or "No visible changes, only CI configuration."
  • Give the command that runs the tests for the change, for example pnpm agent:test --filter <package> -- <test-file>. If there are no tests, give the reason in one line. A bug fix needs a regression test. A feature needs tests

Related Links Section

  • Link to Linear ticket: https://linear.app/n8n/issue/[TICKET-ID]
  • Link to GitHub issues using keywords to auto-close:
    • closes #123 / fixes #123 / resolves #123
  • Link to Community forum posts if applicable
  • If the change has docs, link the n8n-docs PR or the docs follow-up ticket.

Content truncated.

When not to use it

  • →When the repository lacks a pull_request_template.md
  • →When the change does not require a pull request

Prerequisites

gh CLI installedgit repository initializedRepository plan directory access

Limitations

  • →Requires adherence to specific PR title patterns
  • →Security fixes require manual audit of all artifacts

How it compares

Unlike manual PR creation, this skill enforces strict title formatting and automatically integrates implementation plans and security-audited descriptions.

Compared to similar skills

create-pr side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
create-pr (this skill)75moReviewIntermediate
github-workflow-automation116moReviewAdvanced
testing-workflow161yReviewIntermediate
github-actions-templates77moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

github-workflow-automation

ruvnet

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

11113

testing-workflow

amo-tech-ai

Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.

1683

github-actions-templates

wshobson

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.

769

glab

NikiforovAll

Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.

664

gh-fix-ci

openai

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

1234

azure-devops-cli

github

Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI.

436

Search skills

Search the agent skills registry