github

Manage GitHub pull requests, issues, reviews, and repositories via the gh CLI.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill github-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/software-development/github
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill github-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Working with GitHub from an agent or terminal session requires juggling authentication setup, PR lifecycles, issue triage, code review, and CI monitoring, each with its own commands and failure modes. This Skill consolidates those workflows into routed, verified procedures so every claim about remote state is backed by a fresh check rather than guesswork. ## Core Features & Use Cases - Full PR Lifecycle: Create branches, commit with conventional messages, open PRs, watch CI checks, diagnose failures from logs, and merge with squash or auto-merge. - Issue Management and Delivery: Create, triage, label, and close issues, then carry an issue end to end to a verified PR with regression tests and honest CI reporting. - Code Review: Review local diffs or open PRs, leave inline comments, and submit formal approve/request-changes reviews with a structured severity template. - Authentication and Repo Management: Set up gh or git-only auth (including headless device flow), clone, fork, create repos, manage releases, secrets, and branch protection. - Use Case: A user says "fix issue #42 and open a PR." The Skill reads the full issue thread, sweeps for duplicate PRs, validates the premise against current code, implements the fix with a regression test, opens the PR, and shepherds CI to green. ## Quick Start Ask the agent to review pull request number 123 in the current repository and post a summary comment with inline findings.

Frequently Asked Questions about github

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

FAQPage Schema
How do I create a pull request from the command line?▼

Use gh pr create with a title, body, and optional flags like --draft, --reviewer, and --label after pushing your branch with git push -u origin HEAD. Without gh, POST to the GitHub REST API pulls endpoint with curl and a personal access token.

How to review a GitHub PR with inline comments?▼

Fetch the PR locally with git fetch origin pull/N/head:pr-N, review the diff against the base branch, then submit a formal review via gh pr review or the reviews REST endpoint. Inline comments require the head commit SHA, file path, and line number.

Does the gh CLI work on headless Linux servers?▼

Yes, but gh auth login --with-token can hang on keyring-less systems. The workaround is the OAuth device flow with curl, then writing the token directly to ~/.config/gh/hosts.yml, which gh auth status reads without touching the keyring.

How do I check CI status for a pull request?▼

Run gh pr checks for a one-shot status or gh pr checks --watch to poll until completion. With curl, query the commits/{sha}/status and check-runs endpoints for the branch HEAD commit.

Why does git push keep asking for a password on GitHub?▼

GitHub disabled password authentication for git operations. Use a personal access token as the password with a credential helper, or switch to SSH keys configured in ~/.ssh/config.

Can I use the GitHub API without installing the gh CLI?▼

Yes, every workflow has a curl fallback using a personal access token in the Authorization header against api.github.com. The token can come from an environment variable, a .env file, or extraction from the git credential store.