jev-review-action

# Jev Review Action

[](https://github.com/fatwang2/jev-review-action/actions/workflows/ci.yml)

Review submissions and classify pull requests with [TypeSafe Jev](https://typesafe.ai). You define the criteria and categories; Jev returns typed judgments; code applies the policy and updates one PR comment. Jev can be reached through TypeSafe, Vercel AI Gateway or Cloudflare Workers AI, with an ordered fallback chain (see [Jev providers](#jev-providers)).

**Only Jev is used.** Comments come from a fixed template. There is no text-generation model, autonomous agent, or hosted bot server.

An independent personal open-source project by [fatwang2](https://github.com/fatwang2), not an official TypeSafe product. The first consumer is [Awesome Jev](https://github.com/fatwang2/awesome-jev).

## Two modes, one engine

| Mode | Evidence | Example |
| --- | --- | --- |
| `catalog` | 1–10 submitted JSON entries, each with its public GitHub repository's README and source files at an immutable commit | Awesome lists, integration directories, project showcases |
| `pull-request` | PR title, body and changed-file patches | Scope checks and change classification for an ordinary repository |

Policies are JSON. The action does not hardcode Jev ecosystem criteria: replace the categories and questions to review another topic. Examples: [catalog policy](examples/catalog.json), [PR policy](examples/pull-request.json).

## Quick start

1. Copy an example policy to `.github/jev-review.json` on your default branch.
2. Set the repository secret `TYPESAFE_API_KEY` to your own TypeSafe key, or configure another [Jev provider](#jev-providers).
3. Add the workflow below to the default branch. It only runs trusted base-branch code. For production, replace the action version with the full commit SHA fr