pull-request

Creates and submits a GitHub pull request using the gh CLI.

6|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Wyl-cmd/kxns-cli --skill pull-request-wyl-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/Wyl-cmd/kxns-cli/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/Wyl-cmd/kxns-cli --skill pull-request-wyl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually pushing branches and drafting pull requests is repetitive and error-prone, especially when PR titles must follow existing commit message conventions. This Skill automates the checks and submission steps so a clean, well-described PR is created directly from the current branch. ## Core Features & Use Cases - Dirty-change guard: Verifies the working tree has no uncommitted changes before proceeding, preventing incomplete submissions. - Branch validation: Ensures the current branch is a dedicated feature branch rather than main before pushing. - Automated PR creation: Pushes the branch and opens a PR via the gh CLI, writing the title and description in English and matching prior commit message conventions so the squash-merge commit message stays consistent. - Use Case: After finishing a feature on a branch, ask the agent to submit the work; it checks the tree state, pushes the branch, and opens a properly titled PR against main. ## Quick Start Submit my current branch as a pull request to main with a proper 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 create a GitHub pull request from the command line?

Use the GitHub CLI with gh pr create after pushing your branch. This Skill automates that flow: it verifies the working tree is clean, confirms you are on a non-main branch, pushes, and opens the PR with an English title and description.

How to write a pull request title that matches commit message conventions?

The PR title should follow the same convention as prior commit messages in the repository, since it becomes the commit message after a squash merge. This Skill inspects existing commit style and writes the title accordingly.

Can I create a pull request with uncommitted changes in my working tree?

No. The workflow stops immediately if dirty changes exist on the current branch. Commit or stash your changes first so the PR contains a complete, consistent set of modifications.

Why does the pull request workflow refuse to run on the main branch?

Pull requests must originate from a dedicated feature branch, not main. The Skill checks that the current branch differs from main before pushing, ensuring the PR represents an isolated set of changes.

What tool is required to submit a pull request from the terminal?

The GitHub CLI (gh) is required. It handles pushing the branch and creating the PR against the repository's main branch directly from the terminal.