github-cli-help-sweep

Collect help text for gh and all subcommands into per-command artifacts.

Updated Aug 27, 2026

Search Tags:#automation #documentation #gh #inventory #github-cli #command-discovery #help-output

Ready to run

npx skills add https://github.com/JuanGarciaFuture/mobile-practice --skill github-cli-help-sweep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-cli-help-sweep
Source: https://github.com/JuanGarciaFuture/mobile-practice/tree/main/.cursor/skills/github-cli-help-sweep
Command: npx skills add https://github.com/JuanGarciaFuture/mobile-practice --skill github-cli-help-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill inventories the GitHub CLI commands and their help text to provide a complete, portable reference for learning, scripting, and documenting gh usage.

Core Features & Use Cases

Enumerates top-level and nested gh commands by parsing the gh help reference.
Collects per-command help output in a structured artifact set for quick review and offline reference.
Handles special cases like gh completion and gh help extension exec to ensure coverage of edge scenarios.
Supports documentation workflows, onboarding new users, and automation scripting that relies on gh capabilities.

Quick Start

Run the full help sweep to generate a complete GitHub CLI command reference.

Frequently Asked Questions about github-cli-help-sweep

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

FAQPage Schema

How do I list all available GitHub CLI commands and subcommands?▼

To list all GitHub CLI commands, you can inventory the gh command surface by parsing the gh help reference to extract command paths and collect full help text for top-level commands and nested subcommands into structured artifacts.

Can I generate a complete offline reference for gh command help text?▼

Yes, generating a complete offline reference for gh command help text is possible by running gh help reference, executing gh <path> --help for each extracted command path, and saving the per-command outputs to a portable artifact set.

Does the gh CLI help sweep process handle special commands like completion and extension exec?▼

The gh CLI help sweep process handles special cases like gh completion and gh help extension exec explicitly during the command tree enumeration, ensuring complete coverage of edge scenarios and nested extension commands.

What is the best way to document the full GitHub CLI command tree for onboarding?▼

The best way to document the full GitHub CLI command tree is to run a help sweep that enumerates top-level and nested commands, collecting structured per-command help output to support documentation workflows and user onboarding.

Do I need the gh CLI installed to inventory command help outputs?▼

Yes, you need the gh CLI installed and available in your environment to inventory command help outputs, because the process relies on executing gh help reference and running gh <path> --help with stdin redirected to capture text.

Why are some gh subcommands missing from my command help inventory?▼

Some gh subcommands may be missing from your command help inventory if special cases like completion and extension exec are not handled properly during extraction, or if the help reference parsing fails to traverse nested command paths deeply.