by egma-ai · Agent Tool · ★ 152
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
Featured in: Code Review · TypeSafe Jev
git clone https://github.com/egma-ai/jev-code-reviewer.git
Taken from the project's README on GitHub.
None of the 44 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 44 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours.
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 152 |
| Forks | 3 |
| Language | JavaScript |
| Category | Agent Tool |
| License | MIT |
| Quality Score | 63/100 |
| Open Issues | 3 |
| Last Updated | 2026-10-05 |
| Created | 2026-09-19 |
| Platforms | cli, node |
| Est. Tokens | ~14k |
Jev-Code-Reviewer Most PRs that are generated by agents today get YOLO merged because its hard for human mind to comprehend when your agent just suddenly shows up with 230 file changes. This is an attempt to reduce the mental burden by classifying each change in a review to P0, P1, P2. Only P0 are shown by default. The priorities are configurable. The diffs are also show using a natural language.
These tools work well together with jev-code-reviewer for enhanced workflows:
Looking for a jev-code-reviewer alternative? If you're comparing jev-code-reviewer with other agent tool tools, these 2 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
A Claude Code skill that turns PDFs, docs, and codebases into Obsidian study vaults
Power rename/refactor tool for CLI and agent use
Explore other popular agent tool tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 44 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: