github-pr-ops

Create, review, and manage GitHub pull requests via the gh CLI.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/faccomichele/open-claw-team --skill github-pr-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-ops
Source: https://github.com/faccomichele/open-claw-team/tree/main/skills/github-pr-ops
Command: npx skills add https://github.com/faccomichele/open-claw-team --skill github-pr-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of managing GitHub pull requests via the command line, saving development and QA agents time on repetitive PR creation, review, and status tracking tasks.

Core Features & Use Cases

  • PR Creation & Management: Create, view, and list pull requests with proper issue linking, agent identifiers in titles, and relevant labels for traceability.
  • Review & CI Tracking: Fetch PR diffs, post structured review comments, and check CI status to streamline code review and quality assurance workflows.
  • Use Case: A backend development agent can automatically create a feature PR linked to a GitHub issue, while a QA agent can fetch the PR diff, run tests via CI checks, and post review findings directly to the PR without manual CLI input.

Quick Start

Use the github-pr-ops skill to create a new pull request for the feature-branch branch linked to issue #123 with the title "feat: add user auth [dev-backend]" and apply the needs-ai-review label.

Frequently Asked Questions about github-pr-ops

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

FAQPage Schema
How do I automate GitHub pull request creation and code review workflows?

You can automate GitHub pull request creation and code review by using the gh CLI to link issues, post structured review comments, and validate CI status without manual command-line input.

What's the best way to link a pull request to a GitHub issue automatically?

Linking a pull request to a GitHub issue automatically is handled during PR creation by passing the issue number, applying relevant labels, and adding agent identifiers to the PR title for traceability.

Do I need the gh CLI and a GITHUB_TOKEN to manage pull requests programmatically?

Yes, you need the gh and git command-line binaries installed, plus a valid GITHUB_TOKEN environment variable, to interact with GitHub repository APIs and pull request endpoints for PR management.

Can I fetch a PR diff and check CI status from the command line for QA workflows?

Fetching a PR diff and checking CI status from the command line is supported by using gh CLI commands to retrieve changes, run CI checks, and post review findings directly to the pull request.

How does automated PR management work for cross-team code changes?

Automated PR management for cross-team code changes uses agent identifiers in PR titles and structured labels to coordinate development and QA agents, ensuring traceability across teams without manual CLI input.

Are there limitations when using gh CLI for pull request management compared to the GitHub API?

Using gh CLI for pull request management requires local git and gh binaries alongside a valid GITHUB_TOKEN, meaning it operates within the constraints of GitHub API endpoints and local command-line execution environments.