github-operations

Manage pull requests and CI pipelines using the gh CLI and GraphQL API.

Updated Jun 5, 2025
One-click install
npx skills add https://github.com/wangzitian0/finance_report --skill github-operations-wangzitian0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/wangzitian0/finance_report/tree/main/.opencode/skills/domain/github-operations
Command: npx skills add https://github.com/wangzitian0/finance_report --skill github-operations-wangzitian0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines GitHub workflows by automating common tasks like managing pull request reviews, debugging CI pipelines, and performing basic PR operations directly from the command line.

Core Features & Use Cases

  • PR Review Management: Query, resolve, and unresolve review threads on pull requests.
  • CI Debugging: List recent CI runs, view logs for failed runs, and re-run failed jobs.
  • PR Automation: Create, check status, and merge pull requests.
  • Use Case: When a CI build fails, use this Skill to quickly view the logs of the failed run and identify the root cause without leaving your terminal.

Quick Start

Use the github-operations skill to list the last 5 CI runs for the current branch.

Frequently Asked Questions about github-operations

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

FAQPage Schema
How do I view logs for a failed CI run directly from the command line?

To view logs for a failed CI run from the command line, you can use the gh CLI to list recent CI runs and retrieve the specific logs for failed jobs. This allows you to identify the root cause of CI failures without leaving your terminal.

How do I manage GitHub pull request review threads using the CLI?

Managing GitHub pull request review threads using the CLI involves querying existing review threads on a pull request. You can resolve and unresolve these threads directly through gh CLI commands and GraphQL API operations.

Can I re-run failed CI jobs using the gh CLI?

Yes, you can re-run failed CI jobs using the gh CLI. The functionality allows you to list recent CI runs, identify the failed jobs within a pipeline, and trigger a re-run for those specific jobs.

Do I need the gh CLI installed to manage pull requests and CI pipelines?

Yes, the gh CLI is required to manage pull requests and CI pipelines with this approach. The operations rely on gh CLI commands and leverage the GraphQL API for advanced GitHub API tasks like debugging CI failures.

What is the best way to debug CI failures without switching to a browser?

The best way to debug CI failures without a browser is using the gh CLI to list recent pipeline runs and view logs for failed jobs. You can quickly identify the root cause and re-run failed jobs directly from the command line.