github-cli-help-sweep

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.

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.

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.

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.

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.

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.