YOUR PRDOESN'T NEEDA REVIEW.
IT NEEDSEMOTIONALDAMAGE.
The Jev pipeline
CLAUDE WRITES THE ROAST.
JEV DECIDES IF IT SHIPS.
Jev is TypeSafe's decision model. It does not generate jokes. It answers structured questions about the roast versus the actual git diff — then we let you drop it on GitHub. Scored, not guessed.
01
READ THE DIFF
The extension pulls the GitHub PR — title, body, files, the actual patch.
→02
CLAUDE WRITES
One punchline, a roast level, an archetype, GIF searches. Comedy, not a linter dump.
→03
JEV SCORES IT
Eight typed questions vs the diff. Yes/no, pick-one, rate-it. One call. ~200ms. Parallel.
→04
YOU INSERT
If Jev fails hard, Claude rewrites once. Then the roast hits the GitHub comment box.
One API call · eight questions · parallel
What Jev actually asks
PASSED · 187ms
YES / NO
Roast the code, not the person?
YES / NO
Grounded in THIS diff — no invented files?
YES / NO
Safe to post as a public GitHub comment?
YES / NO
Light review, not a linter essay?
YES / NO
Did it clock the obvious (size, leftover logs)?
PICK ONE
Tone: funny-constructive, bland, or mean?
RATE IT
How specific is the joke to this PR?
YES / NO
Short punchline, archetype actually fits?
Hard misses (personal attack, invented files, linter essay) retry Claude once. Soft misses still insert — we log them. If Jev is down, the roast still ships. Fail-open, on purpose.
PRS THAT SHOULD'VE STAYED LOCAL.
Anonymous confessions from the trenches.
“Changed one CSS property.”
47 files changed.
— Anonymous
“Forgot to remove console.log.”
Production.
— Full Stack Developer
“Renamed one variable.”
Opened a 14-file PR.
— Anonymous
“Tests passed.”
Nobody knows why.
— DevOps
“"quick fix"”
+932 lines
— Backend Engineer
“"temporary workaround"”
Created: 2024. Still here: 2026.
— Anonymous
“"works locally"”
Production: 💀
— Senior Developer
“"should be easy"”
Famous last words.
— Tech Lead
CHOOSE YOUR VIOLENCE
Friendly Fire
“Cute PR. A little suspicious though.”
EVERY PR HAS A PERSONALITY.
🧨 The 2AM Hotfix
“Works on my machine.” — Famous last words
📦 The Copy-Paste Special
🛒 The Kitchen Sink
🏗️ The Overengineer
return true;
}
EVERY ROAST DESERVES A REACTION.
Real footage of developers receiving feedback.
← swipe for more →
The reviewer
opening your 847-line PR
Your confidence
after reading the roast
The team
when tests actually pass
Production
Friday at 4:59 PM
Your tech lead
reading the PR description
You
explaining why it's 47 files
The intern
force pushing to main
The senior dev
who wrote the code you're 'refactoring'
try: “when your PR gets merged on the first try”
WHEN THE PR
GETS REVIEWED.
Autoplays muted when you scroll here. Tap the corner button for sound.
You after approving a 3,000-line PR
without reading it
Our AI reviewing your spaghetti code
it's RAW
What senior devs see
when they open your PR
Our deepest technical suggestion
have you tried turning it off and on again?
The code review meeting
going exactly as planned
Your reviewer opening line 847
oh.
THINGS YOUR REVIEWER IS THINKING.
A real-time look inside the approval process.
“I have a meeting in 4 minutes.”
opens your 1,947-line PR
“Seems simple.”
47 files changed
“Let me just quickly review this.”
3 hours later...
“"LGTM"”
(They did not look at it.)
Normal Code Review
RoastMyPR
Jev · checked against the diff
One gives feedback.
The other gives character development.
IT'S EMBARRASSINGLY SIMPLE.
OPEN A PR
Open literally any GitHub pull request.
"small cleanup, I promise"
PRESS THE BUTTON
The big scary one that says 🔥
JEV SCORES THE JOKE
Claude writes the roast. Jev checks it against the actual diff — yes/no, pick-one, rate-it — before anything hits GitHub.
RECEIVE EMOTIONAL DAMAGE
Insert a scored roast, archetype, and reaction GIF. Career therapy still not included.
“This PR has more red flags than a Soviet parade.”