create-pr

Generate Conventional Commits PR titles, templated bodies, and run local checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating pull requests often leads to inconsistent formatting, missing required context, skipped pre-submission checks, and non-compliant titles that fail CI, causing unnecessary review delays and rework for development teams.

Core Features & Use Cases

  • Conventional Commits Formatting: Automatically generates PR titles that follow the Conventional Commits standard with correct type and scope.
  • Templated PR Body: Populates a standard PR template with sections for change description, related issues, risk assessment, and testing details to provide all context reviewers need.
  • Local Pre-Submission Verification: Runs project-specific type checks, linting, tests, and lockfile sync before opening the PR to catch issues early and reduce CI round-trips.
  • Use Case: A developer who just finished a bug fix can use this skill to generate a PR that meets all team conventions, passes local checks, and includes all required context, eliminating back-and-forth with reviewers on formatting or missing information.

Quick Start

Use the create-pr skill to open a pull request for your latest committed changes with a properly formatted title, templated body, and all required local checks run first.

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 conventional commits and local verification checks?

Creating a pull request with conventional commits involves generating compliant PR titles, populating templated PR bodies with required context, and running local verification steps like typecheck, lint, and lockfile sync before opening the PR.

What is the standard format for a PR body to pass code review smoothly?

A standard PR body template includes dedicated sections for change description, related issues, risk assessment, and testing details, providing reviewers with all necessary context to pass code review without formatting rework.

Can I run local checks like typecheck and lint before opening a GitHub pull request?

Yes, you can run local pre-submission verification by executing project-specific type checks, linting, tests, and lockfile sync before opening a GitHub pull request to catch issues early and reduce CI round-trips.

How do I automate PR title generation for conventional commits?

Automating PR title generation for conventional commits requires applying the standard's type and scope rules to your code changes, ensuring the resulting title meets CI and team convention requirements without manual formatting.

How to prevent inconsistent pull request formatting in software development workflows?

To prevent inconsistent pull request formatting, you can automatically populate standard PR templates and generate compliant titles, eliminating missing context and non-compliant formatting that cause unnecessary review delays.

Do I need to link tickets manually when using PR templates for code changes?

No, linking tickets is handled through optional ticket linking features within the PR templating process, automatically connecting your code changes to relevant issues to meet team convention requirements.