Live data from Hacker News

Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

github.com

91–100 of 110 posts

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#91

Earlier quoted context omitted.

it is pretty clear in context given what i was responding to

Maybe I'm misunderstanding, too, but it seems to me that most people responding to you misunderstood your point.

I certainly didn't read it the way they intended!

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#92
post #75
post #61

Earlier quoted context omitted.

One of the most annoying quirks of LLMs for me is the insistence on, after being corrected, loudly noting what wasn't done. After getting it to change something stupid in code, it will leave a comment in the code boasting about how it doesn't do the stupid thing, which to future readers reads like an 'asbestos free!' label on a cereal box.

I have a contrarian take on this: if most people working on the codebase are using the same model, then these comments serve a very useful purpose: they tell the model's future self that despite its tendency towards this solution, it is incorrect and here's why. It encodes useful context right when the model needs it next to avoid making the same error. I imagine this style of commenting is partially responsible for…

If LLMs are any good, like many of you claim, they won’t need these comments. They will ingest the code and know what was done. They won’t need comments about what wasn’t done.

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#93

“It never reimplements git — it shells out to the system git CLI and rebuilds commits with git commit-tree, reusing each commit's original tree so file contents are provably never changed.” Glad the LLM noted this - I was worried this would reimplement git

why can't anyone just do things themselves anymore? it's all LLM crap

People are lazy.

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#95

Earlier quoted context omitted.

Looking at the metadata it says it is a Gnome screenshot. What a pointless and incorrect non-sequitor. exiftool -a -u -g1 ~/Downloads/screenshot.png ---- ExifTool ---- ExifTool Version Number : 13.55 ---- System ---- File Name : screenshot.png Directory : XXX File Size : 1260 kB File Modification Date/Time : 2026:08:11 16:24:37-04:00 File Access Date/Time : 2026:08:11 16:24:41-04:00 File Inode Change Date/Time : 2026…

To be fair, it does really look like a photo of a monitor.

I didn't think that at all. There weren't even any lightning artifacts or glare or anything.

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#96
post #75
post #61

Earlier quoted context omitted.

One of the most annoying quirks of LLMs for me is the insistence on, after being corrected, loudly noting what wasn't done. After getting it to change something stupid in code, it will leave a comment in the code boasting about how it doesn't do the stupid thing, which to future readers reads like an 'asbestos free!' label on a cereal box.

I have a contrarian take on this: if most people working on the codebase are using the same model, then these comments serve a very useful purpose: they tell the model's future self that despite its tendency towards this solution, it is incorrect and here's why. It encodes useful context right when the model needs it next to avoid making the same error. I imagine this style of commenting is partially responsible for…

The problem is that the list of things one shouldn't do is infinite. The things one should do are narrow and get narrower along two independent axes of clarity/wisdom: system requirements and engineer seniority. LLMs overindex on any words given, so you only want to give them negative guidance around truly repeated, almost common-sense pitfalls. But in a large distributed system often the changes come from all different angles, and each agent will find it's own unique failure modes. Those comments will dilute critical context for diverse agents far more than they will help on average, at least for the systems I'm working on, given current claude code chattiness.

One way to clear some of the low-hanging slop is to just have a separate agent code reviewing and pruning any comments that don't stand on their own purely in the context of the diff, but it still doesn't catch it all.

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#97

Earlier quoted context omitted.

why can't anyone just do things themselves anymore? it's all LLM crap

A tool like this never sees the light of day without an LLM. Git is complicated and use case for this is rather niche.

I'm reverse engineering a cherished video game from my childhood. I got to the audio engine part and things got pretty difficult. Managed to map out the locations of the audio data but figuring out which song was which was going to take a long time.

Claude somehow wrote a bespoke one-off Python script to play back the songs straight out of the ROM. I give it the ROM and a hexadecimal address and it just plays it. Converts the data from the ROM into PCM audio samples and pipes them over SSH into termux on my phone where they are played back via SoX play.

Yes, Claude wrote a literal sound synthesizer so I could do this. Claude painstakingly tuned the goddamn synthesizer too, he tweaked it over and over again until the output sounded right based on annoyingly human feedback like "these notes are supposed to be in the background but they are too loud".

This tool turned a painstaking reverse engineering task into a nostalgic listening experience that brought literal tears to my eyes. I mapped out every single song in the game this way.

Without LLMs, none of this would ever have happened.

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#98
post #81
post #80

It looks like the screenshot was an actual photo of someone's monitor. I'm left wondering why print screen wasn't utilized. And for some reason it really makes me not want to touch this project.

I thought it was a semi-transparent window until I read this. The curvature makes that clear, wow!

There is no curvature in the screenshot, only a semitransparent background

Re: Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

#100
This is, funnily enough, something I've been periodically searching for for nearly a decade, and even renewed my search yesterday. For those wondering, my use case is a model Parliament (context: https://news.ycombinator.com/item?id=43474850) and deciding on using git to store the laws, with the commits representing the Acts of Parliament themselves. The problem is that we need to guarantee that every commit has the correct metadata: we do not care at all about the conservation of commit hashes. And if we've accidentally missed a law and need to interactively-rebase it into the git history, it should NOT reset all the subsequent commit dates to the current timestamp. Basically, we're wanting to use git as a historical archive. I'm delighted to have found this.
Post reply on HN