gh

Automate GitHub PR, issue, repo, release, and workflow operations via gh CLI.

54|6|Updated Feb 8, 2017
One-click install
npx skills add https://github.com/amosbird/serverconfig --skill gh-amosbird
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/amosbird/serverconfig/tree/main/.config/skills/gh
Command: npx skills add https://github.com/amosbird/serverconfig --skill gh-amosbird

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh CLI consolidates GitHub operations into a single terminal workflow, reducing context switching and eliminating the need to curl the API for everyday tasks.

Core Features & Use Cases

  • PR management: create, view, list, merge, checkout, diff
  • Issue management: create, view, list, close
  • Repo operations: clone, create, view, fork
  • Release management: create, list, download
  • Workflow management: list, view, run

Quick Start

Authenticate with gh login and start by listing your pull requests with gh pr list.

Frequently Asked Questions about gh

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

FAQPage Schema
How do I automate GitHub PR and issue management from the terminal?

Automating GitHub PR and issue management from the terminal requires using the gh CLI to script operations like creating, listing, and merging pull requests or closing issues without switching to a browser.

Can I manage GitHub workflows and releases in CI pipelines using gh CLI?

Yes, you can manage GitHub workflows and releases in CI pipelines using gh CLI to list, view, and run workflows, as well as create and download releases directly within your automation scripts.

Do I need to use the GitHub API directly to manage repos in local terminals?

No, you do not need to use the GitHub API directly to manage repos in local terminals; the gh CLI enforces using its subcommands to handle cloning, viewing, and forking repos end-to-end.

What is the best way to script GitHub interactions across multiple entities?

The best way to script GitHub interactions across multiple entities is using the gh CLI to consolidate operations like PRs, issues, and repos into a single terminal workflow, eliminating the need to curl the API.

What are the prerequisites for automating GitHub operations with gh CLI?

The prerequisites for automating GitHub operations with gh CLI are having the gh tool installed and authenticated in your local terminal or CI environment before executing any scripted subcommands.

Why should I use gh CLI subcommands instead of direct GitHub API calls?

You should use gh CLI subcommands instead of direct GitHub API calls to reduce context switching and consolidate everyday GitHub operations into a single, streamlined terminal workflow.