gh

Automate GitHub pull request creation, merging, and draft issue generation.

Updated May 24, 2026
One-click install
npx skills add https://github.com/bihaviour/bun-patties --skill gh-bihaviour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/bihaviour/bun-patties/tree/main/.claude/skills/gh
Command: npx skills add https://github.com/bihaviour/bun-patties --skill gh-bihaviour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually managing GitHub pull requests, issues, and merge workflows for this repo requires repetitive command-line entry, strict adherence to the repo's stable-only release model and changeset policies, and consistent formatting for PR bodies and issue metadata. This Skill eliminates that toil by automating the entire workflow with built-in guardrails to prevent errors like missing changesets or accidental publishes.

Core Features & Use Cases

  • Pull Request Creation: Automatically generate draft PRs with structured bodies including change summaries, linked issues, and test plans, plus optional git worktree creation and tracking issue generation with auto-detected labels.
  • Pull Request Merging: Enforce changeset validation before merge, handle optional version bumping, clean up remote branches and local worktrees, and provide clear post-merge release path guidance aligned with the repo's changeset-based publishing flow.
  • Draft Issue Generation: Auto-create well-structured GitHub issues with correct type, priority, and scope labels, plus a standardized body template, derived from short user-provided messages. Use case: A developer working on the Patties framework can type /gh open-pr "add dev-server HMR for island components" to instantly create a draft PR with a linked worktree, tracking issue, and properly formatted body without manual gh command entry.

Quick Start

Use the gh skill to open a draft pull request for your current feature work by typing /gh open-pr followed by a short summary of your changes.

Frequently Asked Questions about gh

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

FAQPage Schema
How do I automate GitHub pull request creation with structured bodies and linked issues?

GitHub pull request merging can enforce changeset validation before merging, handle version bumping, clean up remote branches and local worktrees, and provide post-merge release path guidance aligned with changeset-based publishing flows.

Can I automatically generate GitHub issues with correct type, priority, and scope labels?

This workflow suits monorepo projects requiring standardized PR body formatting, automatic label assignment, changeset validation before merge, and consistent GitHub issue tracking. It enforces a stable-only release model with built-in guardrails.

What's the best way to validate changesets before merging GitHub pull requests?

The best way to validate changesets before merging GitHub pull requests is to use an automated workflow that enforces changeset validation prior to merging, handles optional version bumping, and cleans up branches and worktrees.

How do I clean up git worktrees and remote branches after a pull request merge?

To clean up git worktrees and remote branches after a pull request merge, you can use an automated merging workflow that handles optional version bumping and performs worktree and branch cleanup operations automatically.

Why do I need changeset validation in a monorepo GitHub pull request workflow?

Changeset validation in a monorepo GitHub pull request workflow prevents errors like missing changesets or accidental publishes. It enforces a stable-only release model and ensures consistent formatting for PR bodies and issue metadata.