gh-cli

Automate GitHub workflows and repository operations using the gh CLI.

Updated Oct 31, 2024
One-click install
npx skills add https://github.com/thesammykins/dotfiles --skill gh-cli-thesammykins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-cli
Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/gh-cli
Command: npx skills add https://github.com/thesammykins/dotfiles --skill gh-cli-thesammykins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates GitHub workflows and repository operations using the official gh CLI, enabling repeatable automation for PRs, issues, and repo management.

Core Features & Use Cases

  • Automates common GitHub tasks such as listing PRs, creating issues, merging PRs, and viewing repository data with JSON output for automation.
  • Supports safe, non-interactive operations with clear error handling and status reporting across projects.
  • Use case: A developer wants to script PR creation and issue triage across multiple repos from a single automation workflow.

Quick Start

Run a non-interactive gh command to list open PRs across a repository.

Frequently Asked Questions about gh-cli

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

FAQPage Schema
How do I automate GitHub workflows and manage pull requests from a script?

Yes, you can create issues and merge pull requests across multiple repositories by executing non-interactive gh CLI commands. The process provides structured JSON outputs and includes safety checks for reliable cross-project automation.

Does the gh CLI support non-interactive repository operations for automation?

Querying repository data with the gh CLI returns structured JSON outputs, making it ideal for automation workflows. This format allows you to reliably parse repository information, list open PRs, and process issues across various projects.

What is the best way to list open pull requests across multiple repositories?

Listing open pull requests across multiple repositories is best handled by automating the gh CLI. It executes non-interactive commands with clear error handling and status reporting to safely retrieve PR data in JSON format.

How does error handling work when automating GitHub issues with the gh CLI?

Error handling when automating GitHub issues with the gh CLI relies on clear status reporting and safety checks. This ensures that non-interactive write operations fail safely and provide structured feedback for automation workflows.