create-pr

Automate GitHub pull request creation and auto-merge via gh CLI.

4|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/baleen37/bstack --skill create-pr-baleen37
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/baleen37/bstack/tree/main/plugins/me/skills/create-pr
Command: npx skills add https://github.com/baleen37/bstack --skill create-pr-baleen37

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, and includes scripts (resource) components.

What problem does it solve?

Automates the end-to-end pull-request workflow, turning a sequence of commits into a cohesive PR process without manual, repetitive steps.

Core Features & Use Cases

  • Preflight checks to validate the working tree and branch readiness before PR creation.
  • Automatic PR creation and optional auto-merge to streamline the developer workflow.
  • Base-branch synchronization to ensure the feature branch stays up-to-date with the target branch.
  • CI-ready integration with GitHub Actions and status checks to ensure quality before merge.
  • Use Case: A developer wants to open a PR with a single command after finishing a feature, and have it automatically updated and merged when checks pass.

Quick Start

Command me to create a PR and I will perform preflight, commit, push, PR creation, and optional auto-merge.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from local commits with a single command?

You can automate pull request creation by running scripts that perform preflight checks, commit changes, push to your feature branch, and use the gh CLI to open a PR on GitHub. This streamlines the entire workflow into one command.

What is a preflight check in a GitHub PR workflow?

A preflight check validates your working tree and branch readiness before PR creation. It ensures the feature branch is synchronized with the base branch and that local commits are ready to be pushed and merged without conflicts.

Can I auto-merge a GitHub pull request after CI status checks pass?

Yes, the PR workflow supports optional auto-merge functionality. It integrates with GitHub Actions and status checks to ensure quality gates pass before automatically merging the synchronized pull request.

Do I need the gh CLI installed to automate pull requests from the command line?

Yes, automating pull requests requires the gh CLI, along with git and jq. These dependencies allow the scripts to interact with GitHub's API for PR creation, status checks, and auto-merge operations.

How do I keep a feature branch synchronized with the base branch before opening a PR?

The workflow includes base-branch synchronization to keep your feature branch up-to-date. Scripts automatically synchronize your working branch with the target branch during the preflight stage before pushing and creating the PR.

What's the best way to streamline a multi-branch pull request workflow on GitHub?

The best way to streamline a multi-branch PR workflow is to use scripts that automate preflight, commit, push, PR creation, and auto-merge. This eliminates repetitive manual steps across multi-branch development.