Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Review Precheck

    1

    Does this git diff need a full code review or just a quick look? A fast, free answer with no API key needed.

    Free

    Security scanned
    Review Precheck

    Review Precheck

    Example session with this skill installed

    Run review-precheck on my uncommitted changes. Do they need a full review, or is a quick pass enough?

    • Read your context and instructions
    • Compiled the review precheck

    Summary

    Route: full (exit code 10). Three flags fired, so this change should get a careful review.

    This is real output from a throwaway demo repo, run in offline mode (no API key, no network). The diff did three things: wrapped a file read in a try that ends in except Exception: pass, deleted tests/test_app.py, and added a line to requirements.txt.

    The result

    {
      "route": "full",
      "flags": [
        "dependencies (offline pattern): requirements.txt changed",
        "tests (offline pattern): test file tests/test_app.py deleted",
        "errors (offline pattern): added lines swallow an error (bare except, empty catch, || true)"
      ],
      "note": "offline: pattern checks only, risky logic is not assessed"
    }
    

    Compare: a small, clean change

    The same repo with a one-line change (adding encoding='utf-8' to an open() call) comes back as a quick pass, exit code 0:

    {
      "route": "fast",
      "flags": [],
      "note": "offline: pattern checks only, risky logic is not assessed"
    }
    

    A docs-only diff (README.md) skips the check entirely: {"route": "fast", "flags": [], "note": "docs only"}.

    What the flags mean

    FlagSeen in this diff
    dependenciesrequirements.txt changed
    testsa test file was deleted
    errorsan exception is swallowed with pass
    secrets, auth, schemanothing matched
    risky logicnot assessed offline; only diff size counts (over 30 changed lines never routes fast)

    Next steps

    • Run your full review and tell the reviewer the three flags above, so it starts with the deleted test and the swallowed error.
    • For a model-based second opinion, set a free Codiv OpenJev key as OPENJEV_API_KEY and run it again.
    • Check staged changes with --cached, or a whole branch with main...HEAD.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Hey! This is a small gate you put in front of an expensive code review.

    It reads a git diff and answers one question: does this change need a careful full review, or is a quick pass enough? You get a short JSON answer your agent (or a CI script) can act on.

    What it checks

    Seven questions: secrets, dependencies, auth, schema or migrations, tests, swallowed errors, and risky logic. The wording lives in scripts/review_policy.json, so you can edit it to match your own review policy.

    What you get back

    { "route": "full", "flags": ["tests (offline pattern): test file tests/test_app.py deleted"] }
    

    Exit code 0 means fast (nothing flagged), 10 means full. When it says full, hand the flags to your reviewer so it knows where to look first.

    Two modes

    1. Offline, no key, no network. Regex checks for six of the seven questions: dependency files, schema or migration changes, deleted or skipped tests, secret-shaped strings, auth keywords, swallowed errors. "Risky logic" is judged by size alone: more than 30 changed lines is never called fast.
    2. Model mode, optional. Set a free Codiv OpenJev API key as OPENJEV_API_KEY and the diff is scored by the hosted model instead. Secret-shaped strings are redacted before anything is sent, and the key only goes to api.codiv.ai or a loopback address. A small local model is also possible through jev-tools-setup (see the repo).

    With no key and no offline mode chosen, a code diff routes full with a "Jev unavailable" flag, plus whatever the pattern checks see. It fails safe.

    What you need

    Python 3.10+ and git on your PATH. Standard library only, nothing to pip install.

    Honest limits

    • This is a triage gate, not a code review.
    • Evidence is thin. In model mode it was smoke-tested on two diffs: a rename-only diff routed fast, and a diff with a hardcoded key, a swallowed exception and an emptied test file routed full with the right flags. That is not a benchmark.
    • Offline mode is pattern matching, so it misses anything phrased unusually.
    • Docs-only diffs (.md, .txt, .rst) skip the check and route fast. Diffs over 30,000 characters route full.
    • Untracked files are not in git diff; run git add -N <file> first.
    • It appends one small line per run (timestamp, route, flag count) to ~/.jev-tools/log.jsonl. Diff content and keys are never logged.

    Free and MIT licensed. Source and full measurements: github.com/Rcidshacker/jev-tools

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 10 days ago

    • Free to download with an account

    Requires

    Codiv

    Listed10 days ago

    What's inside

    Frequently Asked Questions