github

Manage GitHub issues, PRs, CI runs, and API queries via gh CLI.

2.8k|212|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/mitsuhiko/agent-stuff --skill github-mitsuhiko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/mitsuhiko/agent-stuff/tree/main/skills/github
Command: npx skills add https://github.com/mitsuhiko/agent-stuff --skill github-mitsuhiko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables interacting with GitHub from the terminal using the gh CLI, reducing context switching and manual navigation.

Core Features & Use Cases

  • PR & CI management: Check PR CI status, list workflow runs, and inspect run details.
  • API access: Retrieve data via gh api for custom insights.
  • Reproducible workflows: Target specific repos with --repo owner/repo when not in a git directory or when working with remote URLs.

Quick Start

gh pr checks 55 --repo owner/repo gh run list --repo owner/repo --limit 10 gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

Frequently Asked Questions about github

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

FAQPage Schema
How do I check pull request CI status from the terminal?

Check pull request CI status from the terminal by running gh pr checks to view workflow runs and inspect CI details directly without using a browser.

How do I query GitHub API for custom repository data?

Query GitHub API for custom repository data by executing gh api commands, allowing you to retrieve specific repository insights and filter outputs using jq syntax.

Do I need gh CLI installed to manage GitHub issues and PRs?

Yes, you need the gh CLI installed and authenticated to manage GitHub issues, PRs, and CI runs from the terminal, ensuring secure access to your repositories.

What's the best way to run GitHub automation tasks outside a git directory?

Run GitHub automation tasks outside a git directory by specifying the target repository explicitly using the --repo owner/repo flag with your gh CLI commands.

Why use gh CLI for GitHub workflows instead of the web interface?

Use gh CLI for GitHub workflows to reduce context switching and manual navigation, enabling quick access to PR status, run details, and repository data directly from the terminal.

Can I list workflow runs for a specific repository using gh CLI?

Yes, you can list workflow runs for a specific repository using gh run list with the --repo owner/repo flag to output recent CI run details directly in the terminal.