pr-operations

Automate GitHub PR lifecycle from creation through merge with gh CLI.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/BenjaminRose805/react-basecamp --skill pr-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-operations
Source: https://github.com/BenjaminRose805/react-basecamp/tree/main/.claude/skills/core/pr-operations
Command: npx skills add https://github.com/BenjaminRose805/react-basecamp --skill pr-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and automates pull request lifecycles across teams, reducing manual overhead and errors.

Core Features & Use Cases

  • PR creation: Create pull requests from feature branches with consistent metadata and templates.
  • CI checks & review: Track CI status, request and incorporate reviews, and enforce approval gates.
  • Merge & cleanup: Apply a chosen merge strategy and perform post-merge cleanup and branch handling.
  • Use Case: A team enforces a 2- or 4-eye review policy and automatically labels, assigns reviewers, and merges when checks pass.

Quick Start

Install and authenticate the GitHub CLI (gh). Create a new PR from your current branch using gh pr create with a descriptive title and body. Monitor CI status with gh pr checks <PR-number> --watch and merge when approved using gh pr merge <PR-number> --squash --delete-branch.

Frequently Asked Questions about pr-operations

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

FAQPage Schema
How do I automate the pull request lifecycle using the GitHub CLI?

Automate the pull request lifecycle by using GitHub CLI commands to create PRs with templates, monitor CI checks, enforce reviews, and execute merges with branch cleanup. This standardizes workflows and reduces manual overhead across multiple repositories.

How do I track CI status and enforce approval gates before a GitHub merge?

Track CI status and enforce approval gates by running gh pr checks with the watch flag to monitor continuous integration. You can request reviews, incorporate feedback, and ensure checks pass before executing the final merge.

What is the best way to standardize PR creation and metadata across repositories?

Standardize PR creation by generating pull requests from feature branches using consistent templates and metadata. This ensures uniform titles, descriptions, and labeling across your development pipelines, reducing manual errors and overhead.

Can I automatically assign reviewers and labels when I create a pull request?

Yes, you can automatically assign reviewers and apply labels during PR creation. This enforces review policies like a 2- or 4-eye check, ensuring consistent assignment and compliance across your team's software pipelines.

Does this PR workflow automation require installing the GitHub CLI?

Yes, this PR workflow automation requires installing and authenticating the GitHub CLI (gh). The procedures rely on gh commands to create pull requests, watch CI checks, and perform merges with post-merge branch cleanup.

How do I handle post-merge cleanup and branch deletion after a GitHub pull request?

Handle post-merge cleanup by executing gh pr merge with the delete-branch flag. This applies your chosen merge strategy, such as squash, and automatically removes the feature branch to keep the repository clean.