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

How to review only the lines a pull request changed with Jev Lint

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

Who it is forA maintainer reviewing pull requests on a busy repo who wants AI-judged feedback on the touched lines without linting the whole codebase.

The problemChecking every file on each pull request is slow and costly, while most findings concentrate in changed code.

The outcomeAnnotated findings on the pull request's changed lines, with the rest of the codebase left out of the run.

What you need first

  • 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

Steps

  1. npm install --save-dev jev-lint
  2. npx jev-lint init
  3. npx jev-lint review --base main (inferred, check the README)
  4. review --base "$GITHUB_BASE_REF" --format github

Prompt for your agent

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.

Caveat. The README says CI can run a review, but no shipped rule blocks a merge until you raise a rule to severity: error, so the check is advisory by default.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page