github

Automates GitHub issue, pull request, and CI run management via the gh CLI with JSON output and --jq filtering.

17|Updated Feb 19, 2026

Search Tags:#github #pull requests #issues #gh cli #api queries #ci runs #json jq

Ready to run

npx skills add https://github.com/ivanrvpereira/.agents --skill github-ivanrvpereira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github
Source: https://github.com/ivanrvpereira/.agents/tree/main/skills/github
Command: npx skills add https://github.com/ivanrvpereira/.agents --skill github-ivanrvpereira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub workflows are slow and error-prone when you have to click through dashboards to find issues, review PRs, and check CI runs.

Core Features & Use Cases

Pull request status & CI visibility: Check whether a PR’s checks passed and inspect workflow runs, including failed steps and logs.
Issue and PR data querying: List issues/PRs and use JSON output with filtering to extract exactly the fields you need.
Advanced API access: Use the GitHub GraphQL/REST API via gh api when the standard subcommands don’t expose the data you want.

Quick Start

Ask your agent to list the last 10 workflow runs for a repository and return them with key metadata using the gh run commands and the repository specified as owner/repo.

Frequently Asked Questions about github

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

FAQPage Schema

How do I check GitHub pull request status and CI runs from the command line?▼

Check GitHub pull request status and CI runs by executing `gh pr` and `gh run` commands via the CLI. This automates retrieving PR check results and inspecting workflow runs, including failed steps and logs, without navigating web dashboards.

How do I list and filter GitHub issues using JSON output?▼

List and filter GitHub issues using JSON output by running `gh issue` commands with `--jq` filtering. This automates advanced data retrieval for repositories, extracting exactly the structured fields you need from local git context or explicit `--repo owner/repo`.

Can I query the GitHub GraphQL or REST API when standard gh cli commands are not enough?▼

Query the GitHub GraphQL or REST API when standard commands lack needed data by using `gh api`. This applies advanced API access techniques to satisfy structured querying needs that standard `gh pr` or `gh issue` subcommands cannot expose.

Do I need the gh cli installed to manage GitHub workflow failures and code review triage?▼

Yes, you need the `gh` CLI installed to manage GitHub workflow failures and code review triage. This requires `gh pr`, `gh run`, `gh issue`, and `gh api` usage with JSON output and `--jq` filtering to function properly.

What is the best way to analyze failed CI workflow steps for a specific repository?▼

The best way to analyze failed CI workflow steps is using `gh run` commands with the repository specified as `owner/repo`. This automates workflow failure analysis by inspecting run logs and extracting key metadata directly through the CLI.