Goal

Integrate Gizzi Code into your CI/CD pipeline to automate code review, changelog generation, and test analysis on every pull request.

Prerequisites

  • An Allternit API key (stored as a CI secret)
  • Node.js 18+ in your CI environment
  • A git repository with PR workflows

GitHub Actions

Code review on PR

Changelog generation

GitLab CI

Permission profiles for CI

Create a restricted profile that limits what the agent can do in CI:
Use it in your pipeline:

Streaming output for CI logs

Use --output-format stream-json for structured output that CI log parsers can consume:

Budget control

Set per-run token limits to prevent runaway costs:

Caching

Cache the global npm package to speed up subsequent runs:

Explanation

  • gizzi exec — Non-interactive mode that prints the response and exits. Safe for CI pipelines.
  • Permission profiles — Restrict what the agent can do in CI (no file edits, no deletions).
  • Token limits — Prevent unexpected cost spikes from large diffs.
  • Streaming output — Structured JSON events are easier to parse in CI log systems.

Next steps

  • Add approval gates — require a human to approve agent suggestions before applying them.
  • Use multi-agent workflows — one agent reviews, another writes tests, another checks security.
  • Integrate with Allternit Evals to measure review quality over time.