jeff (Alurith)
Read-only Go CLI that checks files against your plain-language code rules with Jev, locally or in CI.
Overview
jeff by Alurith is a read-only command-line tool written in Go that semantically checks files against rules you define, such as unclear responsibility or weak error handling, using Jev. It is aimed at developers who want lint-like checks for issues that pattern-based linters cannot express, run locally or as a CI step.
The CLI has check (with config path, text or JSON output and a no-cache option), auth login and logout to store the TypeSafe credential, update to self-update from GitHub releases, and version. Releases ship checksummed binaries for Linux, macOS and Windows on amd64 and arm64, and it can be built from source. It never modifies files. It is Apache-2.0 licensed. Because the rules are plain language, teams can encode conventions that are hard to express as static analysis.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Does this file violate the rule (e.g. unclear responsibility, weak error handling)?(inferred) | yes · no |
How it works
- Define rules in a config file
- Run jeff check on paths
- Each file is sent with the rules to Jev
- Findings are printed as text or JSON; exit status usable in CI
Strengths
- Expresses rules that regex linters cannot
- Read-only by design
- Caching avoids re-checking unchanged files
- Checksummed cross-platform binaries
Caveats
- Sends file contents to the TypeSafe API
- Early version (0.1.0 in README examples)
Getting started
Download a release binary and run `jeff auth login`, then `jeff check [PATH...]`.At a glance
- Type
- CLI
- Status
- beta
- Language
- Go
- Runtime
- CLI
- Has code
- yes
- License
- Apache-2.0
Use cases and integrations
How curated lists describe it
Read-only Go CLI that checks files against rules such as unclear responsibility or weak error handling with Jev, locally or in CI.
MrJev/awesome-jev
Frequently asked questions
What does jeff check?
Whether your files break plain-language rules such as weak error handling, judged by Jev.
Does it change my code?
No, it is read-only.
Can I run it in CI?
Yes, it is designed to run locally or in CI with text or JSON output.
Related projects
Rust code-review gate asking Jev small typed questions about functions and tests, failing CI only on rules measured 80% right.
CLIproductionRustCoding-agent hook that asks Jev one yes/no per project rule on every edit or turn and makes the agent fix any violation.
HookbetaTypeScriptAdvisor for coding agents: git and Stop hooks flag test tampering, secrets and skipped hooks, with optional Jev review findings.
HookbetaCLI and agent commands auditing a git diff against YAML standards packs, scoring each hunk with Jev so agents fix only flags.
Agent skillbetaTypeScriptFuzzy linter hook for Claude Code and Codex where Jev checks each written file against team rules and reports violations at edit time.
HookbetaTypeScriptNatural-language linter combining ast-grep selectors with Jev to catch misleading names, stale comments and tests that miss their claims.
ProjectbetaTypeScript