open-pr

Automate pull request creation from a local git branch.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/heykvnzhao/dotfiles --skill open-pr-heykvnzhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/heykvnzhao/dotfiles/tree/main/skills/open-pr
Command: npx skills add https://github.com/heykvnzhao/dotfiles --skill open-pr-heykvnzhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open PR workflow automation ensures you are not on main/prod, checks that changes are committed, and enables creating a PR with a consistent description.

Core Features & Use Cases

  • Branch validation: verify the current branch is not main or prod and prepare for PR.
  • Diff preview: compare branch against main to show what will be included in the PR.
  • PR creation & formatting: stage/commit changes (if any), draft a PR title and body, and create the PR with gh or via the hosting service.

Quick Start

Open a feature branch, then run the open-pr workflow to generate a PR against main.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I automate pull request creation from a local git branch?

Automating pull request creation involves verifying the current branch, comparing it to main, committing pending work, and publishing the PR via GitHub CLI or a hosting service.

What's the best way to ensure I don't open a pull request from main?

To ensure you don't open a PR from main, use branch validation guards that check the current branch against main or prod and halt the workflow if validation fails.

Can I compare my feature branch to main before generating a PR draft?

Yes, you can compare your feature branch to main using a diff preview to display the exact changes that will be included in the generated pull request.

How do I commit pending work and format a PR title in one workflow?

To commit pending work and format a PR title together, run an automated workflow that stages changes, drafts the PR body, and formats the title before publishing.

Do I need GitHub CLI installed to publish pull requests automatically?

No, you do not strictly need GitHub CLI installed to publish pull requests automatically; the workflow supports optional GitHub CLI integration or a hosting service.