Gst: unified read-only Git state view

Gst launches as a read-only terminal UI that aggregates branch status, staged and work-tree changes, stashes, and the commit graph into a single dashboard [DevTo][GitHub]. The tool is distributed as a Go module; a single go install github.com/lef237/gst/cmd/gst@latest fetches the binary for macOS, Linux, or Windows [GitHub]. When run, gst opens a TUI with tabs for Branch, Diff, Stash, and Graph. The Branch tab shows the current branch name, the upstream remote, and a concise ahead/behind count (e.g., "↑2 ↓1") [DevTo]. The Diff view splits into INDEX (staged) and WORKTREE (unstaged) sections, each marked with the familiar Git markers INDEX, WORKTREE, NEW, and CONFLICT. Pressing y copies the work-tree diff to the clipboard in patch format, while i copies the staged diff – a handy shortcut for sending patches to reviewers or AI assistants [DevTo]. The Graph tab renders a miniature commit DAG, highlighting local vs remote heads. All interactions are read-only: gst never runs push, pull, checkout, commit, merge, or rebase, so it can be safely invoked in CI pipelines or on production servers [GitHub].

Gst matters because it reduces context switches, provides safety for automation, and offers clearer remote tracking. Engineers normally juggle git status, git log --oneline, and git diff in separate panes. Gst collapses those commands into a single, constantly refreshed view, shaving seconds off each iteration of the edit-review-commit loop [DevTo]. Because gst cannot mutate the repository, it can be added to CI jobs to verify branch divergence or to pre-flight a diff before a merge without risking accidental pushes [GitHub]. The ahead/behind counters and visual graph make it trivial to spot stale branches or diverging histories, a common source of merge conflicts in large teams [DevTo].