github – Coding skill for AI agents
Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
Install the github skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/github-5df5b.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /github – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/github-5df5b.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $github – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/github-5df5b.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /github – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/github-5df5b.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /github – then describe the task you want done.
SKILL.md content
GitHub Skill
Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
When to Use
- When the user asks about GitHub issues, pull requests, workflow runs, or CI failures.
- When you need
gh issue,gh pr,gh run, orgh apifrom the command line.
Pull Requests
Check CI status on a PR:
gh pr checks 55 --repo owner/repoList recent workflow runs:
gh run list --repo owner/repo --limit 10View a run and see which steps failed:
gh run view <run-id> --repo owner/repoView logs for failed steps only:
gh run view <run-id> --repo owner/repo --log-failedDebugging a CI Failure
Follow this sequence to investigate a failing CI run:
1. Check PR status — identify which checks are failing:
gh pr checks 55 --repo owner/repo
2. List recent runs — find the relevant run ID:
gh run list --repo owner/repo --limit 10
3. View the failed run — see which jobs and steps failed:
gh run view <run-id> --repo owner/repo
4. Fetch failure logs — get the detailed output for failed steps:
gh run view <run-id> --repo owner/repo --log-failed
API for Advanced Queries
The gh api command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'JSON Output
Most commands support --json for structured output. You can use --jq to filter:
gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
- github-actions – Build, test, and deploy applications using GitHub Actions workflows.
- github-actions-advanced – Design, debug, and harden GitHub Actions CI/CD workflows, including reusable workflows…
- github-actions-debugger – Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows…
- github-actions-templates – Production-ready GitHub Actions workflow patterns for testing, building, and deploying…
- github-automation – Operate GitHub issues, pull requests, branches, checks, workflows, and permissions…
- github-issue-creator – Turn error logs, screenshots, voice notes, and rough bug reports into crisp…
- senior-qa – Generates unit tests, integration tests, and E2E tests for React/Next.js applications…
- github-presence – When the user wants to optimize their GitHub profile, README, or project…