github
Dimillian/Skills/github/SKILL.md
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR, list issues, or query the GitHub API.
What's in it
- GitHub Skill
- Pull Requests
- Debugging a CI Failure
- API for Advanced Queries
- JSON Output
--- name: github description: "Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR, list issues, or query the GitHub API." --- # 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. ## Pull Requests Check CI status on a PR: ```bash gh pr checks 55 --repo owner/repo ``` List recent workflow runs: ```bash gh run list --repo owner/repo --limit 10 ``` View a run and see which steps failed: ```bash gh run view <run-id> --repo owner/repo ``` View logs for failed steps only: ```bash gh run view <run-id> --repo owner/repo --log-failed ``` ### Debugging a CI Failure Follow this sequence to investigate a failing CI run: 1. **Check PR status** — identify which checks are failing: ```bash gh pr checks 55 --repo owner/repo ``` 2. **List recent runs** — find the relevant run ID: ```bash gh run list --repo owner/repo --limit 10 ``` 3. **View the failed run** — see which jobs and steps failed: ```bash gh run view <run-id> --repo owner/repo ``` 4. **Fetch failure logs** — get the detailed output for failed steps: ```bash 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: ```bash 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: ```bash gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"' ```
More agent context in Dimillian/Skills
15 other files this repository gives its agents.
Skill
- app-store-changelogapp-store-changelog/SKILL.md
- bug-hunt-swarmbug-hunt-swarm/SKILL.md
- ios-debugger-agentios-debugger-agent/SKILL.md
- macos-menubar-tuist-appmacos-menubar-tuist-app/SKILL.md
- macos-spm-app-packagingmacos-spm-app-packaging/SKILL.md
- orchestrate-batch-refactororchestrate-batch-refactor/SKILL.md
- project-skill-auditproject-skill-audit/SKILL.md
- react-component-performancereact-component-performance/SKILL.md
- review-and-simplify-changesreview-and-simplify-changes/SKILL.md
- review-swarmreview-swarm/SKILL.md
- swift-concurrency-expertswift-concurrency-expert/SKILL.md
- swiftui-liquid-glassswiftui-liquid-glass/SKILL.md
- swiftui-performance-auditswiftui-performance-audit/SKILL.md
- swiftui-ui-patternsswiftui-ui-patterns/SKILL.md
- swiftui-view-refactorswiftui-view-refactor/SKILL.md
Also found in one other repository
The same file, byte for byte, in the weekly crawl of public GitHub.
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.

