lazygit CLI
lazygit is a terminal Git interface for bisecting regressions: mark good and bad revisions while locating the faulty commit.
- 83,673 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Resets, rebases and custom commands can discard edits or rewrite repository history.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/lazygitDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Resets, rebases and custom commands can discard edits or rewrite repository history.
This is third-party code. Review the repository files before installing.
What it does
lazygit displays Git repository state in a terminal interface. Review diffs, stage lines or hunks, switch branches and manage stashes. Commit history and graphs support inspection of how changes developed. Interactive rebase, cherry-picking and editing older commits help revise history. Worktrees and custom commands are supported. It is human-operated, useful for reviewing an agent’s edits, staged selection and history before committing or pushing.
Who it is for. Developers reviewing edits and assembling commits in a terminal, including changes made by an agent.
Good fit when
- A file contains several changes, and a developer stages selected lines for one commit.
- An author organizes branch commits before review.
- A fix from one commit is carried to another branch.
- A person reviews agent output in a separate worktree before pushing.
Not a fit when
- Shared branch history cannot be rewritten without agreement.
- You need a machine protocol rather than an interactive screen.
- Uncommitted work cannot be risked during reset operations.
Example request
Explain reviewing agent edits in lazygit and staging one hunk without pushing the branch.Limitations
lazygit works with an existing Git repository and does not replace understanding its branches and state. Reset and removal operations can discard uncommitted edits, so preserve working changes first. Rebasing and amending older commits rewrite history and need coordination on shared branches. Custom commands execute in the project context, so inspect configuration and verify the target repository before using them.
How to disable. Quit lazygit. Completed Git operations remain in the repository and need a separate recovery plan.
FAQ
Can I stage part of a file?
Yes. Press `0` on a changed file to focus its diff. Press `a` for line selection, `v` for a range and Space to stage it. Staged changes appear in the lower pane.
Are worktrees supported?
Yes. Select a branch and press `w` to create a worktree and switch to it. Unfinished work on another branch remains in its directory.
Can it rewrite history?
Press `i` to start an interactive rebase, then choose actions for the commits. The `m` menu contains the continue action. Agree on history rewrites before changing a shared branch.
Can I cherry-pick?
Yes. The README specifies `shift+c` to copy the selected commit and `shift+v` to cherry-pick it. Resolve any conflicts and review the resulting diff.
Is it an agent interface?
It is designed for interactive human use. Use appropriate Git commands for scripts.
Discussion
No questions or reviews yet.
Related
CLI toolsGitUI is a terminal Git interface that runs operations asynchronously, keeping the interface responsive during Git work.
The CLI replays Git changes as typing animations to present commits and working-tree edits in the terminal.
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
A CLI that opens a local git diff in the browser like GitHub's Files changed tab; comments copy out as prompts for an agent
A CLI asks questions about a Git diff before push and uses a chosen model to assess how well the developer understands the change.
README in short
Features include bisection and comparing two commits. Documentation provides separate workflow tutorials.