github

Automate GitHub tasks using the gh CLI for issues, PRs, and CI status.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chadyi-king/mission-control-workspace --skill github-chadyi-king
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/chadyi-king/mission-control-workspace/tree/main/skills/github
Command: npx skills add https://github.com/chadyi-king/mission-control-workspace --skill github-chadyi-king

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines GitHub workflows by enabling direct interactions with GitHub via the gh CLI, reducing manual toggling between web and terminal.

Core Features & Use Cases

  • Issue and PR management: Open, list, review, and comment on issues and pull requests from the command line.
  • CI and run visibility: Check CI status and view workflow runs to monitor build health.
  • Advanced data access: Use gh api to fetch specific repository data and title summaries for reporting.

Quick Start

Run gh commands to manage your repository from the terminal.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub tasks using gh CLI commands?

You can automate GitHub tasks using gh CLI by running commands to manage issues, review pull requests, check CI status, and query data via gh api directly from the terminal.

Can I check CI status and workflow runs from the command line?

Yes, you can check CI status and view workflow runs from the command line by executing specific gh CLI commands to monitor build health without switching to the web interface.

How do I fetch repository data using gh api?

Fetch repository data using gh api by executing targeted queries to retrieve specific information and title summaries, returning structured JSON outputs for reporting.

How do I manage pull requests and issues with gh CLI?

Manage pull requests and issues with gh CLI by opening, listing, reviewing, and commenting on them directly through terminal commands, ensuring consistent repository targeting with --repo and explicit URLs.

What is the best way to ensure consistent repository targeting in GitHub automation?

Ensure consistent repository targeting in GitHub automation by using the --repo flag with explicit URLs in your gh CLI commands to precisely direct operations to the correct repository.

Do I need structured JSON outputs when querying data via gh api?

Yes, using --json is required when querying data via gh api to satisfy structured JSON output requirements for precise data extraction and reporting.