pull-request-management

Name: pull-request-management
Availability: InStock
Author: Nice-Wolf-Studio

Automate GitHub pull request workflows using the gh CLI.

Updated Oct 20, 2025

Search Tags:#automation #workflow #GitHub #PR #gh #code-review #pull-request

Ready to run

npx skills add https://github.com/Nice-Wolf-Studio/agent-github-skills --skill pull-request-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pull-request-management
Source: https://github.com/Nice-Wolf-Studio/agent-github-skills/tree/main/skills/pull-request-management
Command: npx skills add https://github.com/Nice-Wolf-Studio/agent-github-skills --skill pull-request-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers streamline GitHub pull request workflows by automating creation, listing, review, and merging tasks via the gh CLI, reducing manual context switching and errors.

Core Features & Use Cases

Create PRs from a feature branch to a base branch with optional labels, reviewers, and draft status.
List and filter PRs by state, base, head, labels, author, or assignee to quickly locate relevant work.
Retrieve pull request details, including files, reviews, comments, and status checks, for quick context.
Merge, rebase, or squash PRs using gh, with optional post-merge actions and messages.
Use case: a developer finishes a feature on branch feature/login, opens a PR to main with a descriptive title and body, assigns reviewers, and merges after checks pass.

Quick Start

Use the pull-request-management skill to create a PR from the feature/login branch to main with a descriptive title and body, then monitor reviews and CI checks.

Frequently Asked Questions about pull-request-management

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

FAQPage Schema

How do I automate GitHub pull request workflows using the gh CLI?▼

Automating GitHub pull request workflows involves using the gh CLI to create, list, view, update, and merge PRs across standard repositories. This reduces manual context switching and errors by streamlining tasks like assigning reviewers and monitoring CI checks.

Can I create a draft pull request from a feature branch to main with labels and reviewers?▼

Yes, you can create a draft pull request from a feature branch to a base branch like main. You can optionally add labels, assign reviewers, and set the draft status directly through the gh CLI to streamline your development workflow.

How do I list and filter pull requests by state, author, or labels?▼

Listing and filtering pull requests is done by querying state, base, head, labels, author, or assignee. This allows you to quickly locate relevant work and retrieve PR details including files, reviews, comments, and status checks for immediate context.

What is the best way to merge or squash a pull request after CI checks pass?▼

The best way to merge, rebase, or squash a pull request is using the gh CLI, which supports optional post-merge actions and custom messages. This automates the final integration step after CI status checks pass successfully.

Do I need to authenticate the gh CLI before managing GitHub pull requests?▼

Yes, you must have the gh CLI installed and authenticated before managing GitHub pull requests. This prerequisite ensures the tool has the necessary permissions to interact with your standard GitHub repositories securely.

What are the limitations of using gh CLI for pull request management?▼

The gh CLI for pull request management is limited to standard GitHub repositories and requires a properly authenticated environment. It automates standard creation, review, and merging tasks but does not replace complex, manual conflict resolution.