githubInteract with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Install via ClawdBot CLI:
clawdbot install steipete/githubUse the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
Check CI status on a PR:
gh pr checks 55 --repo owner/repo
List recent workflow runs:
gh run list --repo owner/repo --limit 10
View a run and see which steps failed:
gh run view <run-id> --repo owner/repo
View logs for failed steps only:
gh run view <run-id> --repo owner/repo --log-failed
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'
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)"'
Generated Feb 15, 2026
Development teams can use this skill to monitor CI/CD pipeline statuses on GitHub pull requests, checking for failed runs and viewing logs for debugging. This helps ensure code quality and streamline deployment processes by quickly identifying issues in automated workflows.
Project managers and developers can list and filter GitHub issues and pull requests using JSON output and jq queries for structured reporting. This enables efficient tracking of tasks, prioritization, and status updates across multiple repositories in agile environments.
Data analysts or DevOps engineers can leverage the gh api command to extract specific data from GitHub, such as PR details or repository metrics, for custom dashboards or integrations. This supports data-driven decision-making and automation in tech operations.
Quality assurance teams can list recent workflow runs and view detailed logs for failed steps to diagnose build or test failures. This accelerates troubleshooting and improves software reliability by providing insights into CI/CD performance.
Companies can integrate this skill into their SaaS platforms to offer GitHub monitoring and management features as part of a larger DevOps toolchain. This adds value by providing real-time insights and automation, attracting customers seeking streamlined development workflows.
IT consulting firms can use this skill to assist clients in setting up and optimizing GitHub workflows, including CI/CD pipelines and issue tracking. This generates revenue through project-based contracts or ongoing support services for improved efficiency.
Educational providers can develop courses or certifications around using the gh CLI for GitHub automation, targeting developers and teams looking to enhance their skills. Revenue comes from course fees, workshops, or certification exams in the tech training market.
💬 Integration Tip
Always specify the --repo flag when not in a git directory to avoid errors, and use --json with --jq for efficient data parsing in scripts.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
Read GitHub repos the RIGHT way - via gitmcp.io instead of raw scraping. Why this beats web search: (1) Semantic search across docs, not just keyword matching, (2) Smart code navigation with accurate file structure - zero hallucinations on repo layout, (3) Proper markdown output optimized for LLMs, not raw HTML/JSON garbage, (4) Aggregates README + /docs + code in one clean interface, (5) Respects rate limits and robots.txt. Stop pasting raw GitHub URLs - use this instead.