github-pull-request

Automate GitHub pull request creation, updates, merging, and release tagging via GitHub CLI.

Updated Jan 31, 2026

Search Tags:#automation #github #release #merge #gh #pull-request #semantic-versioning

Ready to run

npx skills add https://github.com/JordiNodeJS/.github-config --skill github-pull-request

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pull-request
Source: https://github.com/JordiNodeJS/.github-config/tree/main/.github/skills/github-pull-request
Command: npx skills add https://github.com/JordiNodeJS/.github-config --skill github-pull-request

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the GitHub pull request lifecycle by coordinating PR creation, updates, reviews, labeling, validation, and squash-merging with GitHub CLI, reducing manual overhead and human error.

Core Features & Use Cases

Create PRs with consistent bodies using gh pr create and --body-file.
Update PRs, edit titles and descriptions, manage reviews, labels, and checks.
Automate PR merging (squash and merge) and branch deletion, with integrated release tagging.
Publish semantic versioned releases on PR merges with GitHub releases for project visibility.

Quick Start

From a project that uses this skill, run the PR lifecycle commands via gh to create, adapt, merge, and release without leaving the terminal.

Frequently Asked Questions about github-pull-request

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

FAQPage Schema

How do I automate GitHub pull request creation and merging using the command line?▼

Automate the GitHub pull request lifecycle by using the GitHub CLI to handle PR creation, updates, labeling, validation, and squash merging directly from your terminal. This reduces manual overhead and human error during code integration.

What is the best way to automate semantic versioning releases after a pull request merge?▼

Automate semantic versioning releases by triggering automatic release tagging and GitHub release publication immediately after a pull request is squash-merged. This ensures project visibility and consistent version tracking without manual intervention.

Do I need the GitHub CLI installed to automate pull request workflows?▼

Yes, automating pull request workflows requires the GitHub CLI (gh) and git to be installed and authenticated in your environment. These dependencies are necessary to execute commands for PR creation, validation, and merging.

Can I update pull request titles, descriptions, and labels via the terminal?▼

Yes, you can update pull requests, edit titles and descriptions, manage reviews, and apply labels using GitHub CLI commands. This allows you to adapt and manage PR details without leaving your terminal environment.

Does automating squash merging with GitHub CLI automatically delete the branch?▼

Yes, automating PR merging with squash and merge includes integrated branch deletion. This streamlines the workflow by cleaning up feature branches automatically after the pull request is successfully merged into the main project.

How do I create pull requests with consistent bodies using GitHub CLI?▼

Create pull requests with consistent bodies by utilizing the gh pr create command alongside the --body-file parameter. This ensures standardized PR descriptions and reduces manual formatting overhead during project collaboration.