Show HN: Gitlogue – A terminal tool that replays your Git commits with animation (github.com)

159 points by unhappychoice ↗ HN
Gitlogue is a CLI that turns your Git commits into a typing-style replay.

It visualizes diffs line by line, shows the file tree, and plays back each edit as if it were typed in real time.

Key points

• Realistic typing animation

• Syntax-highlighted diffs

• File-tree view

• Replay any commit

• Self-contained CLI

Demo video is in the README.

Repo: https://github.com/unhappychoice/gitlogue

13 comments

[ 4.5 ms ] story [ 30.2 ms ] thread
This looks really cute. I wonder if it'd help with reviews when people have strange PR's
I like it! It's a neat idea :)
This is insanely helpful for debugging other people's code or code you've long since forgotten.
is it able to actually discern the order in which the code was written? would be cool if not to augment it or create a parallel to to actually track this in the manner the code author actually did to write the code - I wonder which functions he/she went to, how he/she wrote code, how long they paused to think, and even what they were thinking!
Actually, looks really cool! Creative idea.
This is cool! It feels fresh and new.

Suggestion for the related projects section: https://gource.io/ Tree view visualization of git history over time.

Finally some external tooling to justify my microcommit habit. (They will play in order here, presumably, instead of the top-to-bottom per-file playback of large commits).

Really nice - thanks for sharing.

> Screensaver — Ambient coding display for your workspace

A coworker years ago screen recorded themselves coding something, then made it their screensaver. Then would just let the screensaver make it look like they were working when they wanted to goof off. This would be prefect for them.

Would work nicely as one of the tools called by the hollywood program.
I thought about such a solution for teaching recently, so I'll try it for the next class :D

I don't mind live coding for students, but it often diverges a bit, I'd rather stick to what's on the repo I prepared with atomic commits.

This could genuinely be a very useful tool for digesting pull requests. A tiny language model could probably do a decent job of ranking hunks by importance to enable replaying back in a more coherent order.