github

Automate GitHub repository, issue, PR, and CI management via gh CLI.

Updated Apr 7, 2026

Search Tags:#workflow #api #github #issues #pr #gh #ci

Ready to run

npx skills add https://github.com/Luzzer/Kraken --skill github-luzzer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github
Source: https://github.com/Luzzer/Kraken/tree/main/skills/github
Command: npx skills add https://github.com/Luzzer/Kraken --skill github-luzzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub management and automation tasks can be repetitive and error-prone; this skill enables direct control of GitHub through the gh CLI.

Core Features & Use Cases

Manage issues and pull requests (create, comment, close, merge)
Inspect CI statuses and run logs
Retrieve repository data via the GitHub API
Quick project setup and maintenance across multiple repos

Quick Start

Authenticate with gh and start managing GitHub issues, PRs, and CI from the command line.

Frequently Asked Questions about github

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

FAQPage Schema

How do I automate GitHub issues and PR management from the command line?▼

Automating GitHub issues and PR management uses the gh CLI to create, comment, close, and merge pull requests directly. This skill runs gh commands to interact with repositories, requiring gh to be installed and authenticated in your local environment.

How can I check CI run statuses and view logs for multiple GitHub repositories?▼

Checking CI run statuses and viewing logs uses the gh CLI to inspect workflow runs across repositories. This skill executes gh run commands to retrieve CI statuses and fetch detailed logs, requiring access to GitHub repositories via local environment or --repo scope.

Do I need to authenticate gh CLI before managing GitHub repositories?▼

Yes, authenticating gh CLI is required before managing GitHub repositories. This skill expects gh to be installed and authenticated locally, using gh commands for issues, PRs, and CI runs, and requires access to GitHub repositories via the local environment or --repo scope.

What's the best way to retrieve repository data across multiple GitHub projects?▼

Retrieving repository data across multiple projects uses the gh CLI api command to fetch information directly. This skill automates GitHub interactions by running gh api commands, expecting access to GitHub repositories via the local environment or --repo scope for data extraction.

Can I use gh CLI to merge pull requests and comment on issues programmatically?▼

Yes, using gh CLI to merge pull requests and comment on issues programmatically is supported. This skill automates these GitHub interactions by executing gh pr and gh issue commands, requiring gh to be installed and authenticated with access to the target repositories.

Why does my GitHub workflow automation fail to fetch repository data?▼

GitHub workflow automation fails to fetch repository data when gh is not installed or authenticated properly. This skill requires gh to be installed and authenticated, and expects access to GitHub repositories via the local environment or --repo scope to execute gh api commands successfully.