github

Run gh CLI commands to retrieve GitHub data and produce structured JSON output.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lalomorales22/penguins --skill github-lalomorales22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/lalomorales22/penguins/tree/main/skills/github
Command: npx skills add https://github.com/lalomorales22/penguins --skill github-lalomorales22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub interactions become faster and more reliable by using the gh CLI from AI prompts, eliminating manual switching between tools.

Core Features & Use Cases

  • Run gh pr checks, gh run list, gh run view, and gh api for advanced queries.
  • Always specify --repo owner/repo when not in a git directory, or use URLs directly.
  • Output can be structured with --json and filtered via jq for automation.

Quick Start

Ask the AI to check a pull request status for a repository using the gh CLI.

Frequently Asked Questions about github

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

FAQPage Schema
How do I check pull request status for a repository using the gh CLI?

To check pull request status, run gh pr checks or gh pr view through AI prompts to retrieve CI statuses and review details, specifying --repo owner/repo when not in a local git directory.

How do I automate GitHub data retrieval across multiple repositories?

Automate GitHub data retrieval by running gh api queries or gh run list commands via AI prompts, filtering outputs with --json and --jq to produce structured data for project management across multiple repos.

Can I use the gh CLI for code review and CI status checks from AI prompts?

Yes, you can use the gh CLI for code review and CI status checks by prompting the AI to execute gh pr checks, gh run view, and gh api commands to fetch and analyze workflow data.

Does the gh CLI require specifying a repo when not in a git directory?

Yes, when not in a local git directory, you must specify the target repository using --repo owner/repo or provide a URL directly to ensure the gh CLI commands execute against the correct project.

What is the best way to structure GitHub CLI output for automation?

The best way to structure GitHub CLI output for automation is using the --json flag to produce structured data and --jq to filter specific fields, enabling seamless integration with AI-driven workflows.

Why use AI prompts with the gh CLI instead of manual GitHub interactions?

Using AI prompts with the gh CLI eliminates manual switching between tools, making GitHub interactions faster and more reliable by directly translating natural language requests into executable gh commands.