Why it exists
The GitHub web UI is good, but for anyone living in the terminal it's a pile of paper cuts. Inline review threads, the review decision, and the PR conversation live in three different places. Rerunning a flaky check is a dropdown buried several clicks deep. Each one is small; together they pull you out of flow.
gh pr checks gets you CI at a glance, but the GitHub CLI has no first-class way to see review threads
with their resolution state. ghx fills that gap, so the whole review loop stays in the terminal.
What it does
ghx comments: inline threads with resolution state, reviews, and the review decision in one viewghx gate: a single merge-readiness verdict with blockers called out, exiting non-zero when blockedghx checks: the CI rollup as bucket counts, failures first, with workflow linksghx resolve/ghx unresolve: manage threads without opening a browser
Built for people and their agents
The human views are readable at a glance, and every command also has a stable --json output and
meaningful exit codes. That makes the same tool a dependable contract for scripts, CI gates, and coding agents
working in the terminal alongside you.
brew install tone-labs/tap/ghx
ghx gate 42 # exits non-zero while the PR is blocked