create-pull-request

Create GitHub pull requests with gh CLI following project conventions.

1|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/YavlPro/YavlGold --skill create-pull-request-yavlpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/YavlPro/YavlGold/tree/main/.kilocode/skills/create-pull-request
Command: npx skills add https://github.com/YavlPro/YavlGold --skill create-pull-request-yavlpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating GitHub pull requests that adhere to project conventions and maintain high quality requires careful coordination of commits, branches, and PR templates, which this skill guides.

Core Features & Use Cases

  • Structured PR creation: guides users to craft well-formed PRs that follow project conventions.
  • Prerequisite checks: ensures gh CLI is installed and authenticated and that the working directory is clean.
  • Automation guidance: provides steps for branch management, base selection, and PR body templating.
  • Use Case: A team needs a reproducible PR process across multiple repositories, ensuring consistent PR descriptions and automated checks.

Quick Start

Create a pull request on your feature branch using gh pr create with a descriptive title and a body that follows your PR template.

Frequently Asked Questions about create-pull-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub pull request that follows project conventions?

To create a GitHub pull request following project conventions, this skill analyzes your commits, manages branch rebasing, and applies PR templating using the gh CLI to ensure structured and consistent PR descriptions.

What do I need to set up before automating pull request creation with gh CLI?

Before automating pull request creation, you need the gh CLI installed and authenticated, and you must ensure your working directory is clean to properly manage branch rebasing and PR templating.

How does branch management work when preparing a feature for code review?

Branch management for code review involves checking for a clean working directory, selecting the correct base branch, and guiding branch rebasing before you execute the gh pr create command for your feature.

Can I use this to automate PRs across multiple repositories with typical CI workflows?

Yes, you can automate pull requests across multiple repositories to ensure consistent PR descriptions and automated checks within typical CI workflows by using standardized branch management and PR templating.

What is the best way to ensure my PR body matches my project's template?

The best way to ensure your PR body matches your project template is to use automation guidance that structures PR body templating and enforces project conventions during the pull request creation process.

Why does pull request creation require checking for a clean working directory?

Pull request creation requires checking for a clean working directory to prevent uncommitted changes from interfering with branch rebasing and commit analysis before you run the gh tool for PR creation.