Repo · Coding & code review
jev-commit
pre-commit hook that makes one Jev call per commit to judge whether the commit message matches the staged diff, and flags filler messages, debug…
Open github.com ↗From the repository
pre-commit hook: one Jev call judges whether your commit message matches the diff, plus debug leftovers, scope creep, and a secret belt
How builders describe it
Pre-commit hook: one Jev call judges whether your commit message matches the staged diff, plus debug leftovers, unmentioned work, and a credential check.
pre-commit hook that makes one Jev call per commit to judge whether the commit message matches the staged diff, and flags filler messages, debug leftovers, unmentioned work and secret-shaped lines.
A pre-commit hook that answers five Jev questions about the commit message and staged diff together, warning on mismatches and blocking only on a credential-shaped line.
Your agent commits forty times a day. It writes the diff, then writes the sentence swearing what the diff does. Nothing reads both. jev-commit is a commit-msg hook that sends the message and the staged diff to Jev in one call and asks five yes/no questions: does the message match the diff, debug…
The decision Jev makes
Label a change, score its risk, pick the relevant file, or decide whether a coding agent should continue.
Where it fits
Code review and coding agents are full of small questions: is this change risky, what kind of fix is this, which file matters. These projects answer them with Jev and route the rest to people or bigger models. All 450 coding & code review projects →