Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From vibe-generate
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.
npx claudepluginhub tiktzuki/project-templates --plugin vibe-generateHow this skill is triggered — by the user, by Claude, or both
Slash command
/vibe-generate:githubThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `gh` CLI to interact with GitHub. Always specify `--repo owner/repo` when not in a git directory, or use URLs
Uses the `gh` CLI to interact with GitHub issues, pull requests, Actions runs, and API queries. Useful for checking PR CI status and debugging workflow failures.
Guides usage of gh CLI for common GitHub operations: PRs, issues, CI checks, logs, and repo metadata.
Provides GitHub CLI commands with JSON output for AI agent workflows: PR checks/status, workflow runs/logs, issue details, repo ops.
Share bugs, ideas, or general feedback.
Use 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)"'