Correlates production error spikes with the exact git commit that caused them.
ErrorMentor reads your error log, detects spikes using a sliding window, then walks backward through git history to find the commit that touched the spiking files — and explains exactly what went wrong.
/ the problem
When errors spike at 2 AM, you need the cause in seconds not minutes. ErrorMentor reads your log, detects the spike automatically, and pins it to the commit that broke things — before you've even opened your laptop.
/ how it works
Sliding window: current error rate > 3× the 30-minute baseline triggers analysis
Identifies which files appear in the spiking error stack traces
Walks backward through commits touching those files in the 10 minutes before the spike
Root cause narrative + exact fix suggestion, ready to share with your team
/ use cases
MIT licensed. One command install. Works in CI today.
/ stay in the loop
Get notified when new tools land, features ship, or a tool reaches 1k stars. No noise. Unsubscribe any time.