github-cli

Automate GitHub CLI workflows for repositories, issues, pull requests, and Actions.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/gabi-agent/openretro --skill github-cli-gabi-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-cli
Source: https://github.com/gabi-agent/openretro/tree/main/skills/github-cli
Command: npx skills add https://github.com/gabi-agent/openretro --skill github-cli-gabi-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub management is often disjointed across multiple interfaces and tools. This Skill centralizes day-to-day GitHub tasks into a single, scriptable CLI workflow, reducing context switching and manual overhead.

Core Features & Use Cases

  • Comprehensive command coverage across repositories, issues, pull requests, Actions, releases, gists, labels, codespaces, and API interactions.
  • Supports REST and GraphQL patterns, secrets/variables, and Projects V2 for automation-ready workflows.
  • Ideal for automation, reproducible setups, and bulk operations across organizations and teams in software development.

Quick Start

Install GitHub CLI, authenticate with gh auth login, and begin by listing repositories with gh repo list.

Frequently Asked Questions about github-cli

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

FAQPage Schema
How do I automate GitHub CLI workflows for repository and project management?

You can automate GitHub CLI workflows by applying scriptable gh commands across repositories, issues, pull requests, Actions, releases, and Gists. This centralizes day-to-day GitHub tasks into a single terminal workflow to reduce context switching and manual overhead.

Do I need to install and authenticate GitHub CLI before managing repositories?

Yes, you need GitHub CLI installed and authenticated to manage repositories. You must run gh auth login to authenticate, then begin by listing repositories with gh repo list to enable repeatable scripting and bulk operations.

Can I use GitHub API interactions for automation-ready workflows?

Yes, you can use GitHub API interactions for automation-ready workflows. The approach supports both REST and GraphQL patterns, secrets/variables, and Projects V2 to enable advanced automation across organizations and teams.

What is the best way to handle bulk operations across GitHub organizations?

The best way to handle bulk operations across GitHub organizations is using scriptable CLI workflows. This supports comprehensive command coverage across repositories, issues, pull requests, Actions, releases, gists, labels, and codespaces for reproducible setups.

Why centralize GitHub tasks into a single CLI workflow?

Centralizing GitHub tasks into a single CLI workflow solves the problem of disjointed management across multiple interfaces. It reduces manual overhead and context switching by applying repeatable scripting and automation patterns directly from the terminal.