github

Automate GitHub issue, PR, and CI tasks via the gh CLI.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/eddmann/jeeves --skill github-eddmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/eddmann/jeeves/tree/main/skills/github
Command: npx skills add https://github.com/eddmann/jeeves --skill github-eddmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub tasks can be repetitive and error-prone; this skill automates issue/PR management and data retrieval via the gh CLI, saving time and reducing manual effort.

Core Features & Use Cases

  • Interact with GitHub issues, PRs, and CI status using gh commands.
  • Retrieve detailed data with gh api and parse structured output.
  • Use cases include triaging issues, approving PRs, and monitoring workflows across repositories.

Quick Start

Authenticate with GitHub using gh and run a sample command to list open issues in a repository.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub issue triage and pull request reviews?

You can automate GitHub issue triage and PR reviews by executing the gh CLI to manage repository data, parse command output, and handle errors robustly across personal and team repositories.

What is the best way to check CI status across multiple GitHub repositories?

Checking CI status across repositories is best handled by using the gh CLI to retrieve API data and monitor workflows, targeting specific repositories explicitly with the --repo flag when not in a git directory.

How do I retrieve structured repository data using the GitHub API?

Retrieving structured repository data is done by using gh api commands to fetch detailed information, which parses the command output for immediate use in your automation workflows.

Do I need to be in a git directory to manage GitHub issues with the gh CLI?

You do not need to be in a git directory to manage issues, but you must explicitly target repositories using the --repo flag to ensure commands execute against the correct repository.

How does explicit repository targeting work for GitHub workflow automation?

Explicit repository targeting works by appending the --repo flag to gh CLI commands, ensuring accurate issue and PR management when you are operating outside of a local git directory.

Why does my automated GitHub PR command fail outside a git directory?

Automated GitHub commands fail outside a git directory because the gh CLI lacks a default context, requiring the --repo flag for explicit repository targeting and robust error handling to prevent failures.