gh-tool

Wraps the gh CLI to return compact structured output for GitHub issues, pull requests, and CI runs.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/vinzenz/workflows --skill gh-tool-vinzenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-tool
Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/gh-tool
Command: npx skills add https://github.com/vinzenz/workflows --skill gh-tool-vinzenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw gh output is verbose, human-formatted, and expensive in tokens for coding agents. This Skill routes GitHub operations through gh-tool, which returns terse TOON output with explicit counts, stable fields, structured errors, and suggested next commands. ## Core Features & Use Cases - GitHub domain coverage: Manage issues, pull requests, reviews, CI runs and logs, releases, labels, repository metadata, projects, secrets, variables, and search from one command grammar. - Safe mutations: Write operations support --dry-run, and stateful changes like close, merge, and cancel are idempotent, reporting already_* when retried. - Raw API access: Run authenticated GitHub API calls via gh-tool api when a dedicated subcommand does not exist. - Use Case: An agent triaging a repository runs gh-tool for a live dashboard of open issues and PRs, then uses gh-tool run view --log-failed to inspect a failing CI job without flooding the context window. ## Quick Start Ask the agent to show the current repository's open issues and pull requests using gh-tool, then drill into any item with its domain subcommand.

Frequently Asked Questions about gh-tool

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

FAQPage Schema
How do I list GitHub issues and pull requests from the command line?▼

Run gh-tool with no arguments to get a dashboard of open issues and pull requests for the current repository. Use gh-tool issue or gh-tool pr subcommands for focused operations on each domain.

How do I view failed GitHub Actions run logs in a terminal?▼

Use gh-tool run view with --log or --log-failed to fetch run logs. Truncated output includes a full_log path, and run watch blocks until completion with a --timeout bound and resumable next commands.

Does gh-tool support dry-run before mutating GitHub?▼

Yes, write operations support --dry-run so you can preview changes before applying them. Stateful mutations like close, merge, enable, cancel, and delete are idempotent and report already_* when the target state is reached.

Can I make raw GitHub API calls with gh-tool?▼

Yes, gh-tool api accepts an HTTP method and path for authenticated raw API calls. This covers endpoints not exposed through the dedicated domain subcommands.

Why does gh-tool fail with authentication errors?▼

gh-tool shells out to the gh CLI, so you must run gh auth login first. Project commands may additionally require gh auth refresh -s project to grant the project scope.