pull-request

Create GitHub pull requests from feature branches via the gh CLI.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Arist12/kimi-cli --skill pull-request-arist12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/Arist12/kimi-cli/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/Arist12/kimi-cli --skill pull-request-arist12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces the time and friction of creating GitHub pull requests by standardizing titles, descriptions, and submission flows.

Core Features & Use Cases

  • Create a pull request from the current feature branch to the target repository.
  • Generate a clear, conventional PR title from recent commits and assemble a descriptive body.
  • Submit the PR via the GitHub CLI (gh) and report status, including links to the PR.

Quick Start

Automatically create a GitHub Pull Request from the current branch with a clear title and description.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I automatically create a GitHub pull request from a feature branch?

You can automatically create a GitHub pull request by using a tool that pushes your feature branch changes via the gh CLI, deriving the PR title from recent commits and assembling the body description.

How does automatic PR title generation work from git commits?

Automatic PR title generation works by analyzing your recent git commits on the feature branch to extract a clear, conventional title, then assembling a descriptive body for the GitHub pull request submission.

Do I need the GitHub CLI installed to automate pull request creation?

Yes, you need the GitHub CLI (gh) installed and authenticated, as the automated pull request creation and submission flow relies on it to push changes and report the PR status and links.

What is the best way to standardize GitHub pull request titles and descriptions?

The best way to standardize GitHub pull requests is to use an automation tool that generates clear, conventional titles from commits and composes structured bodies, reducing friction across repositories and teams.

Can I specify a target repository when automating a GitHub pull request?

Yes, you must specify the target repository when automating a GitHub pull request, allowing the tool to correctly route the submission from your current feature branch via the gh CLI.

Why does my automated pull request submission fail with gh CLI?

Automated pull request submission via the gh CLI can fail due to authentication issues, uncommitted changes on the feature branch, or incorrect target repository specification, requiring built-in error handling to report status.