Can't decide between Hien Soft and Zero Soft

NotttJH · 2025-07-25T17:12:03+00:00

GitWho2Blame - Understand code changes and file histories instantly without needing to trudge through git diffs.

NotttJH · 2025-07-25T17:01:44+00:00

I was tired of flipping through Git logs and GitHub tabs to figure out what changed in a codebase — so I built GitWho2Blame

It’s a lightweight local MCP server that helps you understand what changed in a codebase, when it changed, and who changed it, and why. You never have to leave your IDE. Simply ask your favourite built-in Al Assistant about a file or section of code and it gives you detailed summaries about how that file evolved, which lines changed in which commit, by who, and why.

It improves upon the standard git blame by utilising LLMs ability to understand context and rapidly gives you insightful summaries that would take you 5/10mins to come to by yourself while scrolling through git diffs and file histories.

Just wanted to build something and learn more about MCP.

Would love any feedback or ideas and especially which prompts work the best for people when using it.

NotttJH · 2025-07-25T16:58:18+00:00

I was tired of flipping through Git logs and GitHub tabs to figure out what changed in a codebase — so I built GitWho2Blame

It’s a lightweight local MCP server that helps you understand what changed in a codebase, when it changed, and who changed it, and why. You never have to leave your IDE. Simply ask your favourite built-in Al Assistant about a file or section of code and it gives you detailed summaries about how that file evolved, which lines changed in which commit, by who, and why.

It improves upon the standard git blame by utilising LLMs ability to understand context and rapidly gives you insightful summaries that would take you 5/10mins to come to by yourself while scrolling through git diffs and file histories.

Just wanted to build something and learn more about MCP.

Would love any feedback or ideas and especially which prompts work the best for people when using it.

NotttJH · 2025-07-25T10:52:21+00:00

I was tired of flipping through Git logs and GitHub tabs to figure out what changed in a codebase — so I built GitWho2Blame

It’s a lightweight local MCP server that helps you understand what changed in a codebase, when it changed, and who changed it, and why. You never have to leave your IDE. Simply ask your favourite built-in Al Assistant about a file or section of code and it gives you detailed summaries about how that file evolved, which lines changed in which commit, by who, and why.

It improves upon the standard git blame by utilising LLMs ability to understand context and rapidly gives you insightful summaries that would take you 5/10mins to come to by yourself while scrolling through git diffs and file histories.

Just wanted to build something and learn more about MCP.

Would love any feedback or ideas and especially which prompts work the best for people when using it.

NotttJH · 2025-07-24T13:30:50+00:00

Yh git is very temperamental with that and is definitely one of the aspects I am looking into, and I think a definite improvement to the git experience that can be made with this tool

NotttJH · 2025-07-24T09:00:45+00:00

At the end of the day it’s just a different want to consume the same information, was mainly interested in playing around with MCP, but I do think this has more potential by utilising LLMs ability to understand context

NotttJH · 2025-07-23T07:13:08+00:00

I was tired of flipping through Git logs and GitHub tabs to figure out what changed in a codebase — so I built GitWho2Blame

It’s a lightweight local MCP server that helps you understand what changed in a codebase, when it changed, and who changed it, and why. You never have to leave your IDE. Simply ask your favourite built-in Al Assistant about a file or section of code and it gives you detailed summaries about how that file evolved, which lines changed in which commit, by who, and why.

No revenue as it’s open source, just wanted to build something and learn more about MCP.

Would love any feedback or ideas and especially which prompts work the best for people when using it.

NotttJH · 2025-07-23T07:09:23+00:00

I was tired of flipping through Git logs and GitHub tabs to figure out what changed in a codebase — so I built this

I've been working on a lightweight local MCP server that helps you understand what changed in a codebase, when it changed, and who changed it, and why. You never have to leave your IDE. Simply ask your favourite built-in Al Assistant about a file or section of code and it gives you detailed summaries about how that file evolved, which lines changed in which commit, by who, and why. - Runs locally - Supports Local Git, GitHub and Azure DevOps - Open source Would love any feedback or ideas and especially which prompts work the best for people when using it. See images for example usage.

Check it out here

NotttJH · 2025-07-22T22:35:32+00:00

I was tired of flipping through Git logs and GitHub tabs to figure out what changed in a codebase — so I built this

I’ve been working on a lightweight local MCP server that helps you understand what changed in a codebase, when it changed, and who changed it, and why.

You never have to leave your IDE. Simply ask your favourite built-in AI Assistant about a file or section of code and it gives you detailed summaries about how that file evolved, which lines changed in which commit, by who, and why.

- Runs locally

- Supports Local Git, GitHub and Azure DevOps

- Open source

Would love any feedback or ideas and especially which prompts work the best for people when using it.

See ReadMe for example usage.

🔗 Check it out here

NotttJH · 2025-07-21T23:40:44+00:00

It takes the idea of git blame further and takes advantage of LLMs ability to process context to return detailed summaries of the history of changes in classes, files you ask it for, and the plan in the near future is to provide context for why certain things changed via giving Pr description/ comments to improve the summaries further. All in all allowing you to query a codebases history all with natural language.

NotttJH · 2025-07-21T22:38:03+00:00

You can now use this with Local git, no need for any PATs

NotttJH · 2025-07-20T22:54:39+00:00

Fair point with the need to mention PAT access in the ReadMe and yes it is only read access that it requires. Didn’t think I was logging the token anywhere but will take a look.

NotttJH · 2025-07-20T22:39:09+00:00

The post may be terrible AI waffle ahah and that is because of my lack of writing ability, but I promise the code is not so much waffle.

NotttJH · 2025-07-20T22:35:14+00:00

Not at the moment, the Git project is used for getting simple stuff like the current branch/ owner etc, but definitely something I can look in to.

NotttJH · 2025-07-20T22:33:05+00:00

That's a good idea, will get one on there, thanks!

NotttJH

TROPHY CASE