DEDUPED Hot AI repos, turned into use cases Get 5 a day

What you can do with Jev Lint

jev-lint is a command-line lint tool that uses an AI classifier to flag code, commits, shell scripts and documents whose claims contradict what they actually do.

Trended earlier

mizchi/jev-lint on GitHub

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk.

What do you want to do?

5 use cases

  • Find doc comments that contradict their TypeScript code

    Flag functions whose comments promise behaviour the body does not deliver.

    View prompt
    In the repository <repo-path>, set TYPESAFE_API_KEY, run `npx jev-lint check src --dry-run` to see the planned requests and price, then run `npx jev-lint check src`. Report each finding with file, line, rule id and score, and do not edit code until a human confirms the finding is real.

  • Review only the lines a pull request changed

    Run Jev Lint on a diff so findings land on new code and cost less.

    View prompt
    In the repository <repo-path> on a feature branch, with TYPESAFE_API_KEY set, run `npx jev-lint review --base main` and list each finding with file, line, rule and score. Verify that every finding points at a line the diff actually changed.

  • Check commit messages and staged changes against AGENTS.md

    Judge each commit message against its diff and each change against repo instructions.

    View prompt
    In the repository <repo-path>, with TYPESAFE_API_KEY set, run `npx jev-lint commits --base main` and then `npx jev-lint commits --staged`. Report each finding that cites an AGENTS.md instruction or a commit message mismatch, and confirm each cited instruction exists in the file.

  • Audit shell scripts for hidden effects on the machine

    Flag scripts that download and run code, read secrets or install persistence.

    View prompt
    In the repository <repo-path>, with TYPESAFE_API_KEY set, run `npx jev-lint check scripts --dry-run` to confirm what would be sent, then `npx jev-lint check scripts`. List findings on .sh, .bash or .zsh files with their rule ids, and flag any that a human should read before running the script.

  • Let a coding agent install the skill and run Jev Lint

    Install the Jev Lint skill so an agent can run checks and write project rules.

    View prompt
    In the repository <repo-path>, install the skill with `npx skills add mizchi/jev-lint --skill jev-lint`, then run `npx jev-lint check src --dry-run` and report the planned request count and price. Only after a human approves, run `npx jev-lint review --base main` and list findings with file, line and score.

How to use Jev Lint

  1. Check you have what it needs: Node 24 or newer with npx; A TYPESAFE_API_KEY from https://typesafe.ai, set in the environment (the code being judged is sent to the API); A repository with code to lint, such as a TypeScript src folder.
  2. Open mizchi/jev-lint on GitHub and read the README and license.
  3. export TYPESAFE_API_KEY=...
  4. npx -y jev-lint check examples
  5. npx jev-lint check src --dry-run
  6. npx jev-lint check src

These steps come from our top use case, Find doc comments that contradict their TypeScript code, which also has a copy-paste agent prompt.

Jev Lint alternatives · Best AI repos for Software and DevOps

About this repo

  • Who it is forDevelopers and coding agents who want lint-style checks for mismatches between names, comments and behaviour that type checkers and ESLint do not catch.
  • Why it is hot
  • LanguageTypeScript
  • Sourcegithub.com/mizchi/jev-lint · Back to Hot repos

Requirements

  • Node 24 or newer with npx
  • A TYPESAFE_API_KEY from https://typesafe.ai, set in the environment (the code being judged is sent to the API)
  • A repository with code to lint, such as a TypeScript src folder
Maintain Jev Lint? Add the Featured on Deduped badge

Paste this into your README:

[![Featured on Deduped](https://dedupedai.com/badge/mizchi-jev-lint.svg)](https://dedupedai.com/use-cases/mizchi-jev-lint/?ref=badge)

More badge styles and HTML

Questions about Jev Lint

What is Jev Lint?

jev-lint is a command-line lint tool that uses an AI classifier to flag code, commits, shell scripts and documents whose claims contradict what they actually do. It is an open-source project on GitHub: https://github.com/mizchi/jev-lint.

Who is Jev Lint for?

Developers and coding agents who want lint-style checks for mismatches between names, comments and behaviour that type checkers and ESLint do not catch.

What can I do with Jev Lint?

5 use cases so far, for example: Find doc comments that contradict their TypeScript code; Review only the lines a pull request changed; Check commit messages and staged changes against AGENTS.md. Each has steps and a copy-paste agent prompt.

What do I need to run Jev Lint?

Node 24 or newer with npx; A TYPESAFE_API_KEY from https://typesafe.ai, set in the environment (the code being judged is sent to the API); A repository with code to lint, such as a TypeScript src folder.

What are alternatives to Jev Lint?

Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.

Is Jev Lint safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.