skills.rest
travis-burmaster
travis-burmasterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github

Manage GitHub issues, pull requests, and CI runs using the gh CLI.

Updated Feb 16, 2026
Search Tags:#github#pull requests#issues#gh cli#jq#api queries#ci runs
One-click install
npx skills add https://github.com/travis-burmaster/agentbox --skill github-travis-burmaster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/travis-burmaster/agentbox/tree/main/agentfork/skills/github
Command: npx skills add https://github.com/travis-burmaster/agentbox --skill github-travis-burmaster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interacting with GitHub through the web UI or raw REST API calls is slow and repetitive when you need to check PR status, debug failing CI runs, or query issues from the command line. ## Core Features & Use Cases - Pull Request & CI Inspection: Check PR status with gh pr checks, list workflow runs with gh run list, and view failed step logs via gh run view --log-failed. - Advanced API Queries: Use gh api with --jq filtering to retrieve specific fields from any GitHub REST endpoint. - Structured JSON Output: Combine --json and --jq flags to extract exactly the fields needed from issues, PRs, and runs. - Use Case: A developer sees a failing CI badge, runs gh run list --repo owner/repo to find the failed run, then gh run view <run-id> --log-failed to read only the failing step logs without leaving the terminal. ## Quick Start Ask the agent to check the CI status of a pull request or list recent workflow runs for a specific GitHub repository.

Frequently Asked Questions about github

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

FAQPage Schema
How do I check CI status on a GitHub pull request from the terminal?▼

Run gh pr checks <pr-number> --repo owner/repo to see the status of all CI checks on a pull request. You can also use gh run list to see recent workflow runs and gh run view <run-id> for details.

How to view only failed step logs in a GitHub Actions run?▼

Use gh run view <run-id> --repo owner/repo --log-failed to display logs exclusively from failed steps. This avoids scrolling through successful step output when debugging CI failures.

How do I query GitHub API fields not available in gh subcommands?▼

Use gh api with the endpoint path and --jq to filter fields, for example gh api repos/owner/repo/pulls/55 --jq '.title, .state'. This accesses any GitHub REST API data directly.

Does the gh CLI need to be installed before using GitHub commands?▼

Yes, the gh binary must be installed first. It can be installed via Homebrew with brew install gh or via apt on Debian-based systems, after which authentication with gh auth login is required.

Why do gh commands fail outside a git repository directory?▼

Outside a git directory, gh cannot infer the target repository. Always pass --repo owner/repo explicitly or use full URLs so the command knows which repository to query.

Related Skills

Explore More Software Engineering Skills→
freekmurzefreekmurze
997

fix-github-issue

Automate GitHub issue fixes on feature branches with local tests and PR creation.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

gh-check-ci-status

Check GitHub pull request CI/CD status and workflow runs via gh CLI.

Official
Intermediate
microsoftmicrosoft
190.1k

update-pr

Update an existing pull request with new commits and metadata.

Official
Intermediate
john-data-chenjohn-data-chen
2

github-issues

Create, triage, label, and assign GitHub issues via gh or REST API.

Community
Advanced