create-pr

Create a GitHub pull request with a Conventional Commits title and templated body.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/oElberte/dotfiles --skill create-pr-oelberte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/oElberte/dotfiles/tree/main/private_dot_factory/plugins/marketplaces/factory-plugins/plugins/code-review/skills/create-pr
Command: npx skills add https://github.com/oElberte/dotfiles --skill create-pr-oelberte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a pull request often takes time and consistency work—titles, changelog-style formatting, a useful body, ticket references, and quick local verification before you open the review.

Core Features & Use Cases

  • Conventional Commits PR titles: Generates a type(scope): description title that matches common PR convention checks.
  • Templated PR body: Produces a structured description with risk/impact and testing sections, plus an optional ticket reference.
  • Local verification for code changes: Encourages running typecheck/compile, lint/format, and tests based on what the repo provides before creating the PR.
  • Branch & diff awareness: Uses commit history and stats against the base branch to determine what changed and what scope/type to use.

Use case: You pushed a feature branch and need to submit it for review quickly, with a correctly formatted title/body and confidence that CI won’t fail due to missing checks.

Quick Start

Tell the skill: create a PR from my current branch targeting main with a Conventional Commits title, a templated body, and local verification, linking my ticket if I provide one.

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 pull request with a Conventional Commits title?▼

To create a pull request with a Conventional Commits title, you analyze branch changes against a base branch to derive the type and scope, then use the gh cli to generate a structured PR title formatted as type(scope): description.

What's the best way to format a pull request body for code review?▼

The best way to format a pull request body for code review is using a structured template that includes risk and impact sections, testing details, and optional ticket linkage, ensuring the PR is immediately review-ready.

Do I need to run local verification checks before opening a PR?▼

Yes, you need to run local verification checks before opening a PR to prevent CI failures. This involves running typecheck, compile, lint, format, and tests based on what the repository provides to ensure a clean working tree.

How does branch and diff awareness determine the PR type and scope?▼

Branch and diff awareness determines the PR type and scope by analyzing commit history and diff statistics against the chosen base branch, automatically mapping the nature of code changes to the correct Conventional Commits categories.

Can I link a ticket when creating a GitHub pull request via the command line?▼

Yes, you can link a ticket when creating a GitHub pull request via the command line. The process generates a templated PR body that includes an optional ticket reference section based on the information you provide.

Why does my pull request fail CI checks after pushing a feature branch?▼

Your pull request might fail CI checks after pushing a feature branch if local verification was skipped. Running repo-specific typecheck, lint, and tests locally before using gh pr create ensures the working tree is clean and CI passes.