github

Manage GitHub repositories, issues, pull requests, and CI runs via the GitHub CLI.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/RobbyMo81/assistantrobby --skill github-robbymo81
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/RobbyMo81/assistantrobby/tree/main/skills/github
Command: npx skills add https://github.com/RobbyMo81/assistantrobby --skill github-robbymo81

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets you operate and inspect GitHub repositories, issues, pull requests, and CI runs from the command line, removing the need to navigate the web UI for common repository tasks.

Core Features & Use Cases

  • Use the GitHub CLI to check PR CI status and discover which steps failed for faster triage.
  • List and inspect recent workflow runs, view run details and logs, and run advanced queries with the API for automation.
  • Use case: quickly verify CI for a pull request, pull structured PR fields for reports, or retrieve logs to diagnose failing steps.

Quick Start

Check the CI status for pull request 55 in owner/repo using the gh CLI and report failing steps.

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 for a pull request from the command line?

You can check PR CI status using the GitHub CLI to list workflow runs, identify failing steps, and retrieve specific logs to triage failures directly from your terminal without the web UI.

Can I retrieve structured pull request fields for reporting using the GitHub CLI?

Yes, you can retrieve structured PR fields by running advanced GitHub API queries using gh api endpoints, supporting --json output and --jq filtering to format data for reports.

Do I need the GitHub CLI installed to manage workflow runs and view failed-step logs?

Yes, you require the GitHub CLI (gh) installed in your PATH to manage workflow runs, view run details, and diagnose failing steps through command line operations.

What is the best way to diagnose failing CI steps locally for a GitHub repository?

The best way to diagnose failing CI steps is using the GitHub CLI to view recent workflow run details and pull failed-step logs, enabling fast local triage without navigating the web.

Does this approach support advanced API queries for GitHub repository automation?

Yes, it supports advanced API queries through gh api endpoints, allowing you to automate repository tasks by retrieving filtered JSON outputs directly from the command line.

Why use the command line instead of the GitHub web UI for repository management?

Using the command line removes the need to navigate the web UI for common repository tasks, letting you quickly inspect issues, pull requests, and CI runs locally or remotely.