skills.rest
mlhiter
mlhiterCOMMUNITY
Explore all skills by this author →
GitHub

pr-creator

Create pull requests with explicit base and head branch control.

14|Updated May 27, 2026
Search Tags:#GitHub#branch management#code safety#PR creation#fork-to-upstream
One-click install
npx skills add https://github.com/mlhiter/skills --skill pr-creator-mlhiter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/mlhiter/skills/tree/main/skills/pr-creator
Command: npx skills add https://github.com/mlhiter/skills --skill pr-creator-mlhiter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the complexities of creating pull requests, ensuring that PRs are created with the correct base and head, especially in fork-to-upstream workflows.

Core Features & Use Cases

  • Explicit Base/Head Control: Ensures PRs are created with the correct base and head branches, crucial in fork-to-upstream scenarios.
  • Branch Management: Provides guidance on managing branches, avoiding common mistakes with main or master.
  • Template Filling: Offers detailed instructions for filling out pull request templates accurately.
  • Pre-flight Checks: Suggests running pre-flight checks before creating a PR, enhancing code quality and safety.
  • Use Case: Ideal for developers creating PRs across forks, ensuring the head branch remains owner-qualified and does not fall back to an upstream branch.

Quick Start

Use the pr-creator skill to create a pull request for your changes with the correct base and head branches.

Frequently Asked Questions about pr-creator

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

FAQPage Schema
How do I create a pull request with the correct base and head branches?▼

Creating a pull request with explicit base and head control ensures the correct branches are targeted, especially in fork-to-upstream scenarios. This prevents accidental merges into main or master by keeping the head branch owner-qualified.

How does fork-to-upstream branch management work for PR creation?▼

Fork-to-upstream branch management for PR creation requires setting the base to the upstream repository and the head to your fork. This workflow clarity ensures code safety by verifying the head branch does not fall back to an upstream branch incorrectly.

What are the best practices for filling out pull request templates accurately?▼

Best practices for filling out pull request templates involve following detailed instructions to provide accurate descriptions of changes. Proper template adherence enhances workflow clarity and ensures reviewers understand the code safety implications.

Do I need to run pre-flight checks before creating a PR across forks?▼

Yes, running pre-flight checks before creating a PR across forks is suggested to enhance code quality and safety. These checks validate branch management and ensure your changes are ready for explicit base and head control integration.

Why does my pull request head branch fall back to an upstream branch instead of my fork?▼

A pull request head branch falls back to an upstream branch when explicit base and head control is not applied. Avoid this common mistake in branch management by ensuring the head branch remains owner-qualified during fork-to-upstream workflows.

Related Skills

Explore More Software Engineering Skills→
malinskibeniaminmalinskibeniamin
3

commit-push-pr

Automate commit, push, and pull request creation with CI monitoring.

Community
Advanced
robinebersrobinebers
46

shepherd

Automate GitHub pull request review management until human approval.

Community
Advanced
kenkenmainkenkenmain
1

gh-repo-setup

Automate GitHub repository setup with GitFlow, branch protection, templates, and CI.

Official
Advanced
otomattyotomatty
3

delete-merged-branches

Delete local and remote Git branches merged into a specified base branch.

Community
Advanced