create-pr

Creates GitHub pull requests with standardized titles using gh CLI and Git.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/greptileai/n8n-mirror --skill create-pr-greptileai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/greptileai/n8n-mirror/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/greptileai/n8n-mirror --skill create-pr-greptileai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub pull requests, ensuring that their titles adhere to specific project conventions, which is crucial for CI validation and clear communication.

Core Features & Use Cases

  • Enforces PR Title Conventions: Automatically formats PR titles according to a defined <type>(<scope>): <summary> structure.
  • Supports Various Change Types: Handles features, fixes, performance improvements, documentation changes, and more.
  • Use Case: When you've finished a bug fix and are ready to submit it for review, use this Skill to create the pull request with a title like fix(core): Resolve memory leak in execution engine.

Quick Start

Use the create-pr skill to create a pull request for a new feature in the editor with the summary "Add workflow performance metrics display".

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 GitHub pull request with a title that passes CI validation?

To create a GitHub pull request that passes CI validation, format the title using a specific <type>(<scope>): <summary> structure, automatically enforced by utilizing gh CLI and Git commands for branch pushing and PR creation.

Why do my pull request titles fail CI checks in GitHub?

Pull request titles fail CI checks when they do not follow specific project conventions like defined type, scope, and summary rules, which standardize PR metadata for automated changelog generation and code review.

What is the correct format for a conventional commit pull request title?

The correct format for a conventional commit pull request title is <type>(<scope>): <summary>, supporting various change types including features, fixes, performance improvements, and documentation changes.

How do I automate GitHub PR creation from the command line?

Automate GitHub PR creation from the command line by using the gh CLI and Git commands to push branches and create pull requests with predefined templates and validated title conventions.

Can I use git commands to create a pull request with a predefined template?

Yes, you can use git commands alongside the gh CLI to create a pull request with a predefined template, ensuring the title conforms to specific project conventions for CI validation and clear communication.

Does this PR creation approach support automated changelog generation?

Yes, this PR creation approach supports automated changelog generation by standardizing PR metadata and enforcing title conventions that conform to specific project rules.