create-pull-request

Create GitHub pull requests from feature branches using gh CLI templates.

166|116|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Kilo-Org/kilo-marketplace --skill create-pull-request-kilo-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/Kilo-Org/kilo-marketplace/tree/main/skills/create-pull-request
Command: npx skills add https://github.com/Kilo-Org/kilo-marketplace --skill create-pull-request-kilo-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub pull requests from a feature branch, ensuring adherence to project conventions and reducing manual overhead.

Core Features & Use Cases

  • Prerequisite checks: verify gh CLI availability and authentication, and ensure a clean working directory.
  • Context gathering: detect the current branch, identify the base branch, and summarize recent commits for the PR.
  • PR creation & templates: generate a PR with a structured body using the gh CLI, apply templates, and handle post-creation steps like labeling and assigning reviewers.
  • Use Case: when a developer finishes a feature, this skill opens a PR with a well-formed description ready for review.

Quick Start

Run this skill to create a well-formed PR from your current feature branch using the configured 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 automate GitHub pull request creation from a feature branch?

To automate GitHub pull request creation from a feature branch, use a skill that leverages the gh CLI to detect your current branch, gather commit context, and generate a structured PR body ready for code review.

What do I need to set up before automating a GitHub pull request with the gh CLI?

Before automating a GitHub pull request, you need the gh CLI installed and authenticated, along with a clean working directory on your feature branch to ensure proper branch hygiene before submission.

How does automated branch management handle pull request templates and reviewers?

Automated branch management handles pull request templates by applying predefined structures to the PR body via the gh CLI, and executes post-creation steps to automatically assign reviewers and apply labels.

When should I use an automated pull request workflow instead of manual submission?

You should use an automated pull request workflow instead of manual submission when you finish a feature and need to ensure adherence to project conventions, reducing manual overhead for code review coordination.

Why does automated pull request creation require a clean working directory?

Automated pull request creation requires a clean working directory to ensure branch hygiene, preventing uncommitted changes from interfering with context gathering and commit summarization for the PR body.

Can I use this pull request automation to merge fixes across teammates?

Yes, you can use this pull request automation to merge fixes and coordinate feature work across teammates by generating well-formed descriptions that summarize recent commits for review.