pull-request-tool

Manage pull requests and issues across Copilot APIs and gh-pr-review CLI.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/squirrel289/pax --skill pull-request-tool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-tool
Source: https://github.com/squirrel289/pax/tree/main/skills/tools/pull-request-tool
Command: npx skills add https://github.com/squirrel289/pax --skill pull-request-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified PR and issue management across Copilot APIs and the gh-pr-review CLI reduces complexity and accelerates collaboration.

Core Features & Use Cases

  • Unified interface for PR operations (fetch, list, comment, resolve, merge) across backends.
  • Environment-aware backend selection automatically uses Copilot APIs when available and falls back to CLI otherwise.
  • Designed for software engineering workflows, team review processes, and automation pipelines.

Quick Start

Invoke pull-request-tool to merge a PR in owner/repo using Copilot APIs when available or falling back to gh-pr-review in CLI environments.

Frequently Asked Questions about pull-request-tool

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

FAQPage Schema
How do I manage pull requests when switching between Copilot API and CLI environments?▼

Pull request management across mixed environments is handled by a unified interface that detects available Copilot APIs and falls back to gh-pr-review CLI, standardizing fetch, comment, resolve, and merge operations with predictable JSON outputs.

How does environment-aware backend selection work for PR automation?▼

Environment-aware backend selection for PR automation automatically detects if Copilot APIs are available in the current environment and falls back to the gh-pr-review CLI when they are not, ensuring reliable backend switching without manual configuration.

Can I use standard CLI commands to fetch and resolve PR threads if Copilot is unavailable?▼

You can fetch and resolve PR threads via the gh-pr-review CLI fallback when Copilot is unavailable, allowing standard CLI commands to execute list comments, reply, resolve threads, and merge actions seamlessly across CLI-only environments.

What is the best way to integrate pull request workflows into automation pipelines?▼

The best way to integrate pull request workflows into automation pipelines is using a unified tool that standardizes PR operations into predictable JSON outputs, enabling easy integration across both Copilot-enabled and CLI-only environments.

Do I need to manually configure backend switching for GitHub PR operations across different setups?▼

You do not need to manually configure backend switching for GitHub PR operations, as the unified interface handles environment detection automatically and selects the appropriate Copilot API or gh-pr-review CLI backend without manual intervention.