gh

Orchestrate gh CLI commands for GitHub PRs, issues, releases, and actions.

Updated Feb 11, 2016

Search Tags:#automation #github #cli #issues #gh #workflows #pull-requests

Ready to run

npx skills add https://github.com/Ehrax/dotfiles --skill gh-ehrax

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/Ehrax/dotfiles/tree/main/configs/agents/skills/gh
Command: npx skills add https://github.com/Ehrax/dotfiles --skill gh-ehrax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Navigating GitHub from the command line can be slow and error-prone when managing PRs, issues, workflows, and releases across multiple repositories.

Core Features & Use Cases

Manage pull requests, issues, and comments directly from the terminal, improving turnaround times and reducing context switching.
Run and monitor GitHub Actions workflows, create releases, and quickly inspect repository state without leaving the shell.
Retrieve or mutate repository data via gh, including cloning, forking, and project management tasks.

Quick Start

Create a new pull request in the current repository using conventional commits and a descriptive body.

Frequently Asked Questions about gh

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

FAQPage Schema

How do I manage GitHub pull requests and issues from the terminal?▼

You can manage GitHub pull requests and issues from the terminal by orchestrating gh CLI commands to create PRs, triage issues, and post comments directly without leaving the shell. This reduces context switching and improves turnaround times for code reviews.

Can I monitor GitHub Actions workflows using the gh command line?▼

Yes, you can monitor GitHub Actions workflows using the gh command line to run, check status, and inspect CI/CD execution states across multiple repositories. This allows you to quickly assess repository state and workflow progress directly from your shell.

Do I need gh installed and authenticated to automate GitHub workflows?▼

Yes, you need the gh CLI installed and authenticated to automate GitHub workflows. Once authenticated, you can execute conventional gh commands, subcommands, and flags for precise control over releases, repository management, and project data.

What is the best way to create a new pull request in the current repository via the command line?▼

The best way to create a new pull request in the current repository via the command line is using gh CLI commands with conventional commits and a descriptive body. This automates the PR generation process quickly from your terminal session.

Does this GitHub CLI automation work for managing multiple repositories?▼

Yes, this GitHub CLI automation works for managing multiple repositories by orchestrating commands for cloning, forking, and retrieving repository data. Developers and teams can perform triage and repository management tasks across various projects seamlessly.

Why use gh CLI commands instead of the GitHub web interface for code reviews?▼

Using gh CLI commands instead of the GitHub web interface for code reviews prevents slow and error-prone manual navigation. Automating PRs, issues, and releases directly from the shell accelerates workflows and reduces context switching for developers.