github

Automate GitHub repository, issue, and pull request operations via the gh CLI.

3|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/sawzhang/agent-skills-engine --skill github-sawzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/sawzhang/agent-skills-engine/tree/main/skills/github
Command: npx skills add https://github.com/sawzhang/agent-skills-engine --skill github-sawzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline GitHub administration by enabling direct repository, issue, and pull request operations through the gh CLI inside a unified skill context, reducing manual context switching and command overhead.

Core Features & Use Cases

  • Manage repositories: list, view, clone, and explore
  • Work with issues and pull requests: create, view, checkout, and merge
  • Automate routine GitHub workflows: integrate with scripts and agent prompts to orchestrate tasks

Quick Start

Ask the agent to run gh repo list to see your repositories.

Frequently Asked Questions about github

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

FAQPage Schema
How do I manage GitHub repositories from the terminal?

You can manage GitHub repositories from the terminal by using the gh CLI to list, view, clone, and explore your projects directly without manual context switching.

Do I need gh installed to automate pull request workflows?

Yes, automating pull request workflows requires the gh CLI to be installed and the user to have appropriate permissions to perform actions like creating, checking out, and merging.

Can I create and view GitHub issues using command line commands?

Yes, you can create and view GitHub issues using command line commands executed via the gh CLI to streamline routine administration with minimal manual effort.

What is the best way to automate routine GitHub administration tasks?

Automating routine GitHub administration is best handled by using the gh CLI inside a unified skill context, enabling rapid, repeatable tasks across projects while reducing command overhead.

Are there limitations when using gh for repository management?

The main limitation for gh repository management is the strict requirement for proper permissions, as the user must already have access rights to perform the requested actions on the target repositories.