pull-request

Create and submit GitHub pull requests from a feature branch via gh CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and submission of GitHub pull requests from a feature branch, reducing manual steps and ensuring consistent PR metadata.

Core Features & Use Cases

  • Open a feature branch, push commits, and create a pull request on GitHub using the gh CLI.
  • Provide an English PR title and description that summarize changes and link issues.
  • Support end-to-end PR flow including reviewing and merging when ready.

Quick Start

Instruct the AI to create and submit a PR for the current branch on GitHub with a concise 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 automate GitHub pull request creation from a feature branch?

Automating GitHub pull request creation involves using the gh CLI to push commits from a feature branch and submit a PR with a generated title and description, reducing manual steps and ensuring consistent PR metadata.

Can I generate the PR title and description automatically when submitting code for review?

Yes, generating the PR title and description automatically when submitting code for review is supported. The workflow summarizes your branch changes and links related issues to produce consistent English PR metadata.

Does this PR automation workflow require the gh CLI to submit pull requests on GitHub?

Yes, this PR automation workflow requires the gh CLI to submit pull requests on GitHub. It relies on the gh CLI to handle branch checks, metadata generation, and the final submission with proper review links.

What is the best way to orchestrate an end-to-end pull request flow in a Git workflow?

The best way to orchestrate an end-to-end pull request flow in a Git workflow is to automate branch checks, PR title and description generation, and submission via the gh CLI, ensuring consistent metadata and providing proper review links.

How do I ensure consistent PR metadata across multiple feature branches in GitHub?

To ensure consistent PR metadata across multiple feature branches in GitHub, automate the creation and submission process to generate standardized English PR titles and descriptions that summarize changes and link issues every time.