
Github
- 26 installs
- 46.5k repo stars
- Updated August 3, 2026
- hkuds/nanobot
Interact with GitHub through the gh CLI for issues, pull requests, CI workflow runs, and advanced gh api queries.
About
Documents using the gh CLI to check PR status, list and inspect workflow runs, and query the GitHub API with JSON/jq filtering. A developer uses it when an agent needs to work with GitHub issues, PRs, or CI.
- gh pr checks, gh run list/view --log-failed for CI
- gh api with --jq for structured advanced queries
Github by the numbers
- 26 all-time installs (skills.sh)
- +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #367 of 735 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hkuds/nanobot --skill githubAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 26 |
|---|---|
| repo stars | ★ 46.5k |
| Last updated | August 3, 2026 |
| Repository | hkuds/nanobot ↗ |
What it does
Interact with GitHub through the gh CLI for issues, pull requests, CI workflow runs, and advanced gh api queries.
Files
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:
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-failedAPI 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)"'