Repo · Coding & code review
Semcheck
Go linter whose rules are plain-English questions: AST matchers select nodes and Jev answers one Noul per fragment above the rule's threshold.
Open github.com ↗From the repository
Semantic linter for Go. Write rules as questions in plain English; the AST decides where to look, a model decides if the code is right.
astrocode-qualitygogo-analysisgolanggolangci-lintlinterllmstatic-analysis
How builders describe it
Go linter whose rules are plain-English questions: AST matchers select nodes and Jev answers one Noul per fragment above the rule's threshold. It runs standalone, under go vet, and as a golangci-lint plugin, with cached answers so runs only ask about changed code.
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 →