DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to run a scripted code review in CI with Agav

Call Agav run from a pipeline to review a folder and produce output a script can read.

Short answer: Install Agav in the CI job with curl -fsSL https://agav.dev/install.sh | bash; then make sure the provider credentials your model needs are available to the job; run agav run "review the code in src/" from the repository root. All steps.

Authorization notice. Agav is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The CI job needs model provider credentials stored as secrets, and the README does not describe how they are passed to the binary.

Remote script. The install step downloads and runs a script from Agav.dev inside your CI environment.

Who it is forA CI maintainer who wants an automatic review step on code in a project folder for each build.

The problemManual review of every change does not scale, and interactive tools do not fit a pipeline.

The outcomeThe pipeline prints a review of the target folder, and the result can be captured for later steps.

What you need first

  • A terminal on your machine
  • The Agav binary, installed with the install command in the README
  • An API key for a cloud provider, or a local Ollama setup
  • A project folder or repository you want the agent to work in

Steps

  1. Install Agav in the CI job with curl -fsSL https://agav.dev/install.sh | bash.
  2. Make sure the provider credentials your model needs are available to the job.
  3. Run agav run "review the code in src/" from the repository root.
  4. Enable the JSON Schema output option described in the CLI reference at docs.agav.dev/reference/cli so a later step can parse the result. (inferred, check the README)
  5. Fail or pass the job based on the review output your team defines.

Prompt for your agent

Using the Agav repo at prapaa-ai/agav, run `agav run "review the code in <target-folder>"` from <repo-root> in a non-interactive shell. Expected output: a review text or structured output for that folder. Verify that the command exits and the output names at least one file inside <target-folder>.

Caveat. The README names the JSON Schema output option but does not show its flag, so confirm the exact syntax in the CLI reference before wiring it into a pipeline.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for prapaa-ai/agav and "Run a scripted code review in CI"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer