Skip to content
bmf-san

bmf-san/ggc

Live in production

📖 Full documentation: https://bmf-san.github.io/ggc/

A modern Git CLI tool with both traditional command-line and interactive incremental-search UI.

284 3 since joining 10GoPush 1d agoListed 17d ago3 open issuesMIT
clideveloper-toolsgitgogolangsdg-17sdg-9
  • Go96.2%
  • Shell3.1%
  • Go Template0.4%
  • Makefile0.2%
  • Dockerfile0.0%
View on GitHub

Report a problem

1 Review

ggc feels like a focused, practical developer tool rather than a toy Git wrapper. The idea is easy to understand: keep normal one-shot commands like ggc status, ggc add, ggc commit, and ggc log simple, but also give users an interactive fuzzy-search UI when they just run ggc. That combination is useful because it serves both people who already know what they want to type and people who want a discoverable Git workflow without memorizing every command.

The project gives off strong maintenance signals. The repo has around 280 stars, about 10 forks, 900+ commits, MIT licensing, a code of conduct, contributing guide, security policy, Go Report Card, Codecov, CI, CodeQL, Dependabot, OpenSSF Scorecard badges, and Go docs links. The release story also looks healthy, with many tagged releases and prebuilt binaries for macOS, Linux, and Windows. Installation is especially approachable: Homebrew, go install github.com/bmf-san/ggc/v8@latest, a shell installer, and downloadable release archives are all covered.

The README is one of the stronger parts of the project. It shows the core workflow quickly, links to full documentation, includes demo GIFs, explains interactive mode, and points users toward command references, recipes, configuration, aliases, keybindings, troubleshooting, and shell completions. The structure of the repo also looks clean for a Go CLI: cmd, internal, docs, tools, test, generated completions, GoReleaser config, lint config, and benchmark/test files all suggest the maintainer is thinking about distribution and long-term upkeep.

The main thing I would improve is positioning. Git already has several popular TUI or helper tools, so ggc should make its unique angle very explicit near the top: “scriptable Git shortcuts plus searchable workflow builder” is more compelling than just “A Go Git CLI.” I would also add a few concrete before/after examples showing when ggc is better than raw Git, lazygit, tig, or gitui. Finally, because this tool wraps potentially destructive Git commands, the docs should clearly explain safety behavior around branch deletion, clean, reset-like operations, and workflow execution previews.

Overall, ggc looks polished, useful, and unusually well-maintained for a personal CLI project. It is easy to install, easy to try, and the interactive workflow mode gives it a real reason to exist beyond being a thinner spelling of Git.