gh

Manage GitHub resources with structured gh CLI commands.

Updated Apr 17, 2026

Search Tags:#git #pull request #github #cli #issue management

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/jiesou/dotfiles/tree/main/exact_dot_agents/exact_skills/exact_0connect/exact_gh
Command: npx skills add https://github.com/jiesou/dotfiles --skill gh-jiesou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of interacting with the GitHub CLI (gh) by providing structured commands and handling pagination, search, and repo targeting, thus streamlining the management of GitHub resources.

Core Features & Use Cases

Structured Output: Utilizes --json to get structured data from gh commands.
Pagination and Silent Truncation: Handles pagination and silent truncation for lists.
Repo Targeting: Override default repository with --repo flag.
Search vs List: Differentiates between searching and listing commands for better control.
Use Case: For example, use gh pr list --search "closed" to find all closed pull requests.

Quick Start

List all closed pull requests in the current repository with gh pr list --search "closed".

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 using the command line?▼

To manage GitHub pull requests and issues via the command line, you can use the GitHub CLI (gh). This approach provides structured commands to list, search, and handle pagination for repository resources efficiently.

How do I list closed pull requests in a specific GitHub repository?▼

You can list closed pull requests in a specific GitHub repository using the gh command with search filters. Utilize the --search flag, like `gh pr list --search "closed"`, and override the default target with the --repo flag.

How do I get structured JSON output from GitHub CLI commands?▼

To get structured JSON output from GitHub CLI commands, use the --json flag. This ensures the command returns structured data, making it easier to parse pull requests, issues, and other GitHub resources programmatically.

Do I need to install and configure the GitHub CLI separately to manage repositories?▼

Yes, you need the GitHub CLI installed and configured separately to manage repositories. This setup is a prerequisite before you can execute structured commands to handle pagination and search capabilities for your GitHub resources.

What is the difference between searching and listing GitHub issues with gh?▼

The difference between searching and listing GitHub issues with gh lies in filtering control. Listing provides standard repository views, while searching uses specific criteria within commands to find targeted pull requests or issues.

How do I handle silent truncation and pagination when listing GitHub pull requests?▼

To handle silent truncation and pagination when listing GitHub pull requests, use the structured gh commands provided. These commands manage large lists automatically, ensuring you retrieve complete result sets without manual pagination logic.