Shelling out to git blame in a streaming Node fashion.
-
Updated
Aug 14, 2017 - JavaScript
#
git-blame
Here are 8 public repositories matching this topic...
AI-powered git history explainer - understand why code exists
-
Updated
Apr 3, 2026 - JavaScript
AI-powered git archaeology. Understand why any line exists — traces through renames, refactors, and the full history. 🔍
debugging cli open-source ai code-analysis npm-package forensics developer-tools archaeology hacktoberfest git-history git-blame npx anthropic claude-code
-
Updated
Feb 27, 2026 - JavaScript
gitwhen — pinpoint when a string, line, or file changed in git history. Zero deps wrapper around git log -S / git blame / git log --diff-filter.
nodejs git cli devtools git-history git-blame git-log history-search git-search file-history code-history git-archaeology voiddo git-pickaxe line-history change-history
-
Updated
May 18, 2026 - JavaScript
AI-powered Chrome extension that surfaces Git blame context and Groq LLM explanations directly on hover within GitHub — built on Manifest V3 with service worker architecture, dual-layer caching via chrome.storage.local, and zero backend dependency.
javascript css chrome-extension html open-source github-api ai service-worker vanilla-javascript developer-tools git-blame chrome-storage groq manifest-v3 llm
-
Updated
Mar 21, 2026 - JavaScript
Answer "how much of this codebase did I actually write?" — runs git blame across your entire repo and shows your authorship stats: lines owned, ownership %, language breakdown, team leaderboard, and top files.
-
Updated
Mar 20, 2026 - JavaScript
Improve this page
Add a description, image, and links to the git-blame topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the git-blame topic, visit your repo's landing page and select "manage topics."