Reviq reviews your code with AI. Paste a snippet, drop in a batch of files, point it at a local git repository, or wire it up to your GitHub/GitLab pull requests so every PR gets reviewed automatically. Runs fully offline with a local model, or use your own API key for Claude, OpenAI, Groq, or OpenRouter — your choice.
| Code analysis (paste/upload files) | Local AI model management |
|---|---|
![]() | ![]() |
| Git repository review | Analysis history |
|---|---|
![]() | ![]() |
Requirements: .NET 10 SDK, and git available on your PATH if you want to review local repositories.
git clone <repo-url>
cd Reviq
dotnet build
cd src/Reviq.API
dotnet run
Open http://localhost:5000 in your browser — that's the whole app, no separate frontend server needed.
You need at least one working provider before you can run a review:
localhost:11434 and LM Studio at localhost:1234.src/Reviq.API/appsettings.json (or, better, to appsettings.Development.json / user-secrets so it never ends up committed) under the matching AI:<Provider>:ApiKey entry, then restart the app. It'll show up as configured in the provider switcher.Git:GitHub:Token / Git:GitLab:Token to appsettings.json — this is what Reviq uses to post comments and commit statuses back to your repo.Git:GitHub:WebhookSecret (or Git:GitLab:WebhookSecret) — this is what stops anyone who finds your webhook URL from triggering fake reviews. Use the same value when creating the webhook in the next step.https://<your-server>/api/webhook/github (or /gitlab), triggered on pull request / merge request events, with the secret from step 2.This needs Reviq to be reachable from GitHub/GitLab, so for real usage you'll want to deploy it somewhere public (or tunnel it, e.g. with ngrok, for testing). If you skip step 2, webhooks still work, just without signature verification.
Architecture, project layout, tech stack, and the current list of known limitations live in docs/ARCHITECTURE.md.
C#
52.6%
JavaScript
27.2%
CSS
14.0%
HTML
6.1%
Reviq reviews your code with AI. Paste a snippet, drop in a batch of files, point it at a local git repository, or wire it up to your GitHub/GitLab pull requests so every PR gets reviewed automatically. Runs fully offline with a local model, or use your own API key for Claude, OpenAI, Groq, or OpenRouter — your choice.
| Code analysis (paste/upload files) | Local AI model management |
|---|---|
![]() | ![]() |
| Git repository review | Analysis history |
|---|---|
![]() | ![]() |
Requirements: .NET 10 SDK, and git available on your PATH if you want to review local repositories.
git clone <repo-url>
cd Reviq
dotnet build
cd src/Reviq.API
dotnet run
Open http://localhost:5000 in your browser — that's the whole app, no separate frontend server needed.
You need at least one working provider before you can run a review:
localhost:11434 and LM Studio at localhost:1234.src/Reviq.API/appsettings.json (or, better, to appsettings.Development.json / user-secrets so it never ends up committed) under the matching AI:<Provider>:ApiKey entry, then restart the app. It'll show up as configured in the provider switcher.Git:GitHub:Token / Git:GitLab:Token to appsettings.json — this is what Reviq uses to post comments and commit statuses back to your repo.Git:GitHub:WebhookSecret (or Git:GitLab:WebhookSecret) — this is what stops anyone who finds your webhook URL from triggering fake reviews. Use the same value when creating the webhook in the next step.https://<your-server>/api/webhook/github (or /gitlab), triggered on pull request / merge request events, with the secret from step 2.This needs Reviq to be reachable from GitHub/GitLab, so for real usage you'll want to deploy it somewhere public (or tunnel it, e.g. with ngrok, for testing). If you skip step 2, webhooks still work, just without signature verification.
Architecture, project layout, tech stack, and the current list of known limitations live in docs/ARCHITECTURE.md.
C#
52.6%
JavaScript
27.2%
CSS
14.0%
HTML
6.1%