lazygit
$ brew install lazygitGit workflows, staging, and history browsing from the terminal.
- lazygit fits git & github well, especially for git workflows, staging, and history browsing from the terminal.
- 25,723 homebrew installs (30d).
- Verify with `lazygit --version` first.
- Best treated as a human-first terminal tool.
- Output is mostly text-first, so verify results before scripting around it.
Lazygit guide
Git workflows, staging, and history browsing from the terminal. Built by Jesse Duffield.
Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.
When to apply
- git workflows, staging, and history browsing from the terminal.
- You work with git workflows and want a fast terminal interface.
- You need git workflows.
- You need staging.
- You need history browsing.
Quick reference
brew install lazygitlazygit --versionlazygitOpen CLI × skills.sh
Open CLI integrates lazygit with the right skills.sh companions so you get the tool and the workflow together.
Git Workflow
Recommended pairingOpen CLI recommends this skills.sh skill because it fits git workflows. Use cleaner branches, reviews, and merge flows around Git-based CLIs.
$ npx skills add https://github.com/supercent-io/skills-template --skill git-workflowUse lazygit together with the Git Workflow skills.sh skill. Start with safe inspection commands, summarize what you find, and ask before any step with side effects.
Why this tool
- lazygit fits git & github well, especially for git workflows, staging, and history browsing from the terminal.
- 25,723 homebrew installs (30d).
- Verify with `lazygit --version` first.
Watch-outs
- Automation can be brittle.
- Output is mostly plain text.
- Start with read-only or dry-run commands.
Example workflow
1. lazygitSafe start
Install lazygit.
Run `lazygit --version` first.
Start with `lazygit`.
Install the CLI and make sure it is on your PATH.