Git Archaeology #0 — What If Git History Could Tell You Who Your Strongest Engineers Are?

git log + git blame. That's all it takes. What Is This? Engineering Impact Score (EIS, pronounced "ace") is an open-source CLI tool that quantifies engineering impact from Git history alone. No external APIs. No AI tokens. Just git log and git blame. brew tap machuz/tap && brew install eis cd your-repo eis That's it. Here's what you get: Why I Built This Commit counts. PR counts. Lines of code. Easy to measure — and all meaningless. A typo fix and a system-wide architecture change both count as "one PR." A generated lockfile adds thousands of lines. Commit frequency varies wildly between engineers. Yet inside every team, people know who the strongest engineers are. "That person writes code that lasts." "That person touches everything but nothing improves." Those intuitions exist, but they're not measurable. I wanted to turn gut feeling into numbers — and I wanted those numbers to come from a source that can't be gamed by politics: the git history itself. The Telescope Over the