github

Manage GitHub issues, pull requests, workflow runs, and releases via gh CLI.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/billyfranklim1/claude-skills --skill github-billyfranklim1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/billyfranklim1/claude-skills/tree/main/plugins/github/skills/github
Command: npx skills add https://github.com/billyfranklim1/claude-skills --skill github-billyfranklim1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes friction when working with GitHub from the terminal by providing concise gh CLI commands to inspect pull requests, runs, issues, and releases so you can triage CI, manage issues, and publish releases without searching documentation.

Core Features & Use Cases

  • CI and PR triage: Commands and examples to list workflow runs, view run details, and surface failed steps for rapid debugging.
  • Issue management: Quick commands to list, view, create, and close issues across repositories.
  • Advanced queries and releases: Guidance on using gh api, --json and --jq for structured output and creating or listing releases programmatically.
  • Use Case: When a pull request's CI fails, use the provided commands to find the most recent run, inspect which steps failed, and collect logs for the author.

Quick Start

Check CI status for pull request 55 in owner/repo, open the related workflow run details, and retrieve the failed step logs.

Frequently Asked Questions about github

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

FAQPage Schema
How do I triage failed GitHub Actions workflow runs from the command line?

You can triage failed CI workflow runs by using the gh CLI to list recent runs, view specific run details, and retrieve the failed step logs directly from your terminal. This allows rapid debugging without navigating the web interface.

How do I manage GitHub issues across different repositories using gh CLI?

To manage GitHub issues across repositories, use the gh CLI with the --repo owner/repo flag to list, view, create, and close issues in non-git directories. This enables efficient issue tracking across multiple repository contexts.

Can I get structured JSON output from gh CLI commands for advanced queries?

Yes, you can get structured output from gh CLI commands by applying the --json and --jq flags, or by using gh api for advanced queries. This allows programmatic extraction of pull requests, runs, and releases data.

Do I need to authenticate the gh CLI before managing pull requests and releases?

Yes, you must have the gh CLI installed and authenticated to manage pull requests and releases. Authentication is required to access repository data and execute commands across owner/repo contexts.

What is the best way to publish GitHub releases programmatically via the terminal?

The best way to publish GitHub releases programmatically is using gh CLI commands to create and list releases. This removes friction by providing concise commands for release publishing directly from the terminal.

How does gh CLI handle repository maintenance tasks in CI systems?

The gh CLI handles repository maintenance in CI systems by providing commands to inspect pull requests, workflow runs, issues, and releases. It uses --repo owner/repo for non-git directories to apply to CI triage and tracking tasks.