github

Manages GitHub issues, pull requests, and CI runs via the gh CLI.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/Tau_agent --skill github-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/shalevamin/Tau_agent/tree/main/tau-agent-main/skills/github
Command: npx skills add https://github.com/shalevamin/Tau_agent --skill github-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It eliminates the need to switch to the GitHub web UI for routine repository operations by letting you manage issues, pull requests, and CI runs directly from the command line with the gh CLI. ## Core Features & Use Cases - Pull Request Management: List, view, create, merge, and check CI status of PRs with structured JSON output. - Issue Operations: Create, close, comment on, and triage issues with label and date filtering. - CI/Workflow Inspection: View workflow run status, fetch failed step logs, and re-run failed jobs. - Use Case: Before merging a feature branch, run gh pr checks to verify CI passed, review the PR summary with additions and deletions, then merge with a squash commit — all without leaving the terminal. ## Quick Start Ask the agent to check the CI status and review summary of pull request number 55 in your repository using the gh CLI.

Frequently Asked Questions about github

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

FAQPage Schema
How do I check GitHub PR status from the command line?

Use gh pr checks followed by the PR number and --repo owner/repo to see CI status. For full details including title, author, and change stats, run gh pr view with --json fields and --jq filtering.

How to view failed GitHub Actions logs with gh CLI?

Run gh run view with the run ID and the --log-failed flag to show only failed step logs. You can list recent runs first with gh run list --limit 10, then re-run failures using gh run rerun --failed.

Does the gh CLI work with GitLab or Bitbucket repositories?

No, the gh CLI only works with GitHub repositories. GitLab and Bitbucket require their own CLIs (glab and Bitbucket API tools), and local git operations like commit or push should use git directly.

Why does gh CLI fail with authentication errors?

The gh CLI requires one-time authentication via gh auth login before any repository operations. Verify your authentication state with gh auth status and re-login if the token has expired or scopes are insufficient.

When should I use gh api instead of gh pr or gh issue commands?

Use gh api for queries not covered by dedicated subcommands, such as fetching specific fields, listing labels, or bulk operations across repositories. It supports --jq filtering and --cache for rate-limit-friendly repeated queries.