open-pr

Generate and publish GitHub pull requests with diff-based titles and structured bodies.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill open-pr-webdevcody
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/open-pr
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill open-pr-webdevcody

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly create a correct GitHub pull request by generating a review-ready title and Summary/Test-plan from the full branch diff, while preventing common mistakes like using the latest commit title or targeting the wrong base branch.

Core Features & Use Cases

  • Diff-grounded PR drafting: Synthesizes a PR title and Summary bullets from the cumulative changes between the base branch and your branch (using git diff <base>...HEAD), not just the latest commit message.
  • Deterministic, reviewer-friendly body: Produces a structured body with a Summary section and a concrete checkbox-style Test plan, designed for reviewer engagement.
  • Safe creation workflow: Runs preflight checks (repo remote presence, upstream tracking, commit presence, base branch detection) and requires a confirmation gate before publishing; opens as draft when commits indicate WIP or when requested.

Quick Start

Ask the assistant to open a pull request from your current branch and include a title and Summary/Test plan tailored to what changed.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I generate a pull request title from a git branch diff?

To generate a pull request title from a branch diff, this Skill analyzes the cumulative changes between your base branch and HEAD using git diff. It synthesizes a review-ready title and structured Summary bullets from the actual code changes rather than relying solely on the latest commit message.

How do I create a draft PR from the command line?

You can create a draft PR from the command line by asking the assistant to open a pull request. The workflow detects WIP commits or user requests to automatically publish your branch as a draft, requiring a confirmation gate before finalizing the creation.

How do I ensure my GitHub PR targets the correct base branch?

To ensure your GitHub PR targets the correct base branch, this workflow runs preflight checks using GitHub CLI for default base branch discovery. It verifies repo remote presence, upstream tracking, and commit presence before attempting to publish the pull request.

How do I write a structured test plan for a GitHub pull request?

To write a structured test plan for a GitHub pull request, this process generates a deterministic, reviewer-friendly body from your branch diff. It produces a concrete checkbox-style Test plan alongside a Summary section designed specifically for reviewer engagement.

What is the best way to automate PR creation from a local git branch?

The best way to automate PR creation from a local git branch is using a workflow that performs upstream-aware pushing and diff-based drafting. This approach handles base-branch targeting and generates reviewer-ready documentation through GitHub CLI before enforcing a confirmation gate.

Why does my automated pull request use the wrong base branch?

Your automated pull request may target the wrong base branch if default branch detection is skipped. This workflow prevents that mistake by enforcing preflight checks that discover the correct base branch via GitHub CLI before generating the diff and publishing.