github

Manage GitHub PRs, issues, and CI via terminal using gh CLI.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill github-brikkoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/skills/github
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill github-brikkoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually navigating GitHub's web UI for common repository tasks like checking PR status, reviewing CI logs, or managing issues is slow and inefficient for developers working with GitHub repositories daily.

Core Features & Use Cases

  • PR & Issue Management: Check pull request status, reviews, merge readiness, create or close issues, and add comments directly from the terminal.
  • CI/CD Monitoring: View workflow run status, pull failed job logs, and re-run failed CI jobs without switching to the GitHub web interface.
  • GitHub API Access: Query repository data, list releases, collaborators, and labels using structured JSON output for custom automation workflows. For example, a developer can quickly verify if their open PR has passed all required CI checks before requesting a final review.

Quick Start

Use the github skill to check the CI status and review details for pull request #123 in the owner/repo repository.

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 and CI/CD workflow runs from the terminal?

You can check pull request status and CI/CD workflow runs from the terminal by executing commands via the official GitHub CLI. This eliminates manual web UI navigation, allowing developers to review PR details, view workflow run statuses, and pull failed job logs directly.

Do I need the GitHub CLI installed and authenticated to manage repositories locally?

Yes, the GitHub CLI must be installed and authenticated to manage repositories locally. This terminal-based interaction requires the official gh CLI to execute commands for pull requests, issues, workflow runs, and API queries against your GitHub-hosted projects.

What is the best way to query GitHub API data like releases and collaborators without the web UI?

Querying GitHub API data like releases and collaborators without the web UI is best done by executing structured API commands through the GitHub CLI. This returns structured JSON output, enabling custom automation workflows and direct repository data extraction from the terminal.

Can I create, close, or comment on GitHub issues directly from my command line?

Yes, you can create, close, and comment on GitHub issues directly from your command line. The GitHub CLI supports terminal-based issue tracking, allowing developers to manage issues and add comments without switching to the GitHub web interface.

How does terminal-based GitHub repository management compare to using the web interface?

Terminal-based GitHub repository management compares favorably to the web interface by eliminating slow manual navigation. It streamlines developer workflows for PR triage, CI/CD monitoring, and issue tracking directly from the command line, significantly reducing context switching.

Why does my GitHub CLI workflow run monitoring fail to pull failed job logs?

GitHub CLI workflow run monitoring may fail to pull failed job logs if the CLI is not properly authenticated or lacks sufficient repository permissions. Ensure the official gh CLI is installed, authenticated, and has access to the specific GitHub-hosted project.