Your branch is clean, but history is a mess.
You run git log and the noise swallows the signal. You know git rebase can rewrite the story. You also know reading commits line by line is slow. This is where lnav changes the way you debug your past.
Why Git Rebase and Lnav Belong Together
git rebase is not just a cleanup tool. It’s a scalpel for your commit history. It lets you drop useless commits, merge related changes, and replay work on a cleaner base. That precision is wasted if you can’t read the commit impact fast.
lnav turns logs into live insight. It’s built for structured data, and with Git, it becomes a real-time forensic lens. Pass Git’s logs into lnav, filter by time, author, or message, and see patterns you’d miss in plain text.
Rebase, then inspect. Or inspect, then rebase. Both ways, the combo works.
Set It Up in Seconds
- Use
git log --pretty=format:'%h %ad %an %s' --date=iso > commits.log to export commits in a structured form. - Open it in
lnav:
lnav commits.log
- Navigate with search and filters to spot the noisy commits or suspicious gaps.
Once you see the gaps, git rebase -i <base-hash> gives you control. Drop the noise. Reword unclear messages. Group related commits.
When It Matters Most
Mass refactors, merge-heavy branches, or handover reviews. Anytime history is bloated or tangled, rebase plus lnav gives you clarity before you push upstream. No more guessing which commit caused the shift. You see it. Then you fix it.
Unlock It Without Pain
You don’t need to fight complex log pipelines or spend hours scripting. This workflow becomes muscle memory. And if you want to see it in action—visualized, automated, and live in minutes—check out hoop.dev.
Your repo should tell the truth. With git rebase and lnav, it will.