Code review has a blind spot, and it’s history. A reviewer looking at a three-line change to auth/session.py sees three reasonable lines. They don’t see that this file was in the middle of three outages in the last ten weeks, or that the obvious fix for those outages never worked.
I built a small bot for DejaVu, my incident-response agent with long-term memory, that puts that history into the pull request. If a PR touches a file with an incident history, the bot comments with every incident that file was part of. This post covers how it works and the two security problems I had to fix before I’d trust it.
Repo: https://github.com/cybersleuth25/Deja-Vu
What the comment looks like
Open a PR that changes auth/session.py and the bot posts this:
DejaVu: incident history for this pull request
⚠️ auth/session.py was involved in 3 outages
INC-0007 2026-08-27 SEV2: Users logged out at random: session store evictions
INC-0025 2026-10-27 SEV1: Login 500s: JWT verification failing after key rotation
INC-0029…