skills.rest
kma-core
kma-coreOFFICIAL
Explore all skills by this author →
GitHub

pr

Creates draft pull requests on GitHub with conventional commit titles and structured descriptions.

Updated May 28, 2026
Search Tags:#git#code review#pull request#conventional commits#github#gh cli#draft pr
One-click install
npx skills add https://github.com/kma-core/windmill --skill pr-kma-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/kma-core/windmill/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/kma-core/windmill --skill pr-kma-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request manually requires analyzing branch changes, writing a clear title and description, running local review, and handling enterprise-edition companion changes. This Skill automates that entire workflow so every PR follows a consistent, review-ready format. ## Core Features & Use Cases - Automated branch analysis: Inspects commits and diffs against main to build an accurate PR summary, change list, and test plan. - Conventional commit titles: Enforces <type>: <description> formatting (feat, fix, refactor, docs, chore, perf) with an [ee] prefix when enterprise files change. - Mandatory pre-PR review: Invokes the local-review skill before creating the PR so issues are fixed and committed first. - EE companion PRs: Detects changes in the symlinked windmill-ee-private repo and opens a linked companion draft PR there. - Use Case: After finishing a bug fix on a feature branch, ask the assistant to open a PR; it reviews the code locally, pushes the branch, and returns a draft PR URL with a structured body. ## Quick Start Ask the assistant to open a draft pull request for the current branch using the pr skill.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a draft pull request on GitHub from the command line?▼

Use the GitHub CLI with `gh pr create --draft --title "<type>: <description>" --body "..."` after pushing your branch. This Skill automates that flow by analyzing commits, running a local review, pushing to origin, and returning the PR URL.

How to write a pull request title using conventional commits?▼

Use the format `<type>: <description>` where type is feat, fix, refactor, docs, chore, or perf. Keep it under 70 characters, lowercase, imperative mood, with no trailing period, and prefix with `[ee]` if enterprise files were modified.

What should a pull request description include?▼

A clear PR body includes a Summary section explaining what and why, a Changes section listing specific modifications, and a Test plan checklist describing how to verify each change. This Skill generates that structure automatically from the branch diff.

Does this Skill handle changes in the windmill-ee-private repository?▼

Yes. Since `*_ee.rs` files are symlinks to windmill-ee-private, the Skill checks that repo for uncommitted or unpushed changes and creates a companion draft PR there referencing the main PR number.

Why must a local review run before creating the pull request?▼

The Skill mandates invoking the `local-review` skill before opening the PR so issues are caught and fixed locally first. If problems are found, they must be committed before the PR is created, keeping review cycles short.

Related Skills

Explore More Software Engineering Skills→
tldrawtldraw
50.1k

clean-copy

Reimplements a git branch on a new branch with a clean, reviewable commit history.

Official
Intermediate
xxihxxih
1

pr-lifecycle

Coordinate PR lifecycle actions from creation through merge.

Community
Intermediate
abretonc7sabretonc7s

pr-readiness-check

Detect missing tests, documentation, and guideline violations in pull request diffs.

Community
Intermediate
vercelvercel
142.0k

gh-stack

Manage stacked pull requests and dependent branches using the gh-stack CLI extension.

Official
Advanced