Change-impact review for GitHub pull requests

See what
your PR
breaks.

For each pull request, Zenik finds the code that the change can break. It shows every caller, every service, and every test that the change affects, in more than 8 languages. Other reviewers tell you what changed. Zenik tells you what breaks.

No code-read permission · Your code never leaves your environment · Your own LLM key
zenik-ai[bot] — PR #128
Changed symbols
3
Impacted callers
14
Services hit
3
billing-api Cross-service refunds.py:88 calls create_refund() ⚠ 3 callers
web Parallel Same logic in lib/refund.ts:24 — keep in sync 1 file
worker Tests test_refund.py:12 covers the changed path 2 tests
One call graph for all of your languages
PythonTypeScriptGoRubyJava& more
How it works

Install. Index. Review.

You do these three steps one time. After that, Zenik reviews every pull request before an engineer reads the diff.

01 / Install

Install the GitHub App

The install screen shows all the permissions. Permission to read your code is not on the list. Zenik cannot open your repository.

02 / Index

Add one workflow file

Your own pipeline builds the call graph. GitHub OIDC does the authentication, so you keep no shared secrets. Later runs take seconds.

03 / Review

Zenik reviews every pull request

Zenik writes short comments and adds a check. Write the comment /zenik fix, and Zenik commits the fix to the branch. It changes only the affected files.

What it finds

The callers that a search does not find.

Cross-service callers

The caller in a different service, in a different language. One graph covers more than 8 languages.

Parallel implementations

The same logic in a second service. Zenik shows it, so that you can keep the two copies in sync.

Renamed symbols

Zenik finds the callers of a renamed symbol and of a renamed file.

The related tests

Zenik lists the tests that cover the changed code. You do not search the test suite.

Security

We never read your code.

Other reviewers copy your repository to their servers. Zenik does not copy your repository. The analysis runs in your own pipeline, and the GitHub App has no permission to read your code.

No code-read permission

Read the permission list on the install screen before you accept.

Your code never leaves your environment

Your own pipeline builds the graph and does the analysis. Your code stays on your machines.

Keyless authentication

Zenik uses GitHub OIDC. There are no shared secrets and no tokens to rotate.

Your own LLM key

The agent uses your OPENAI_API_KEY. The key stays in your job. Zenik never receives it.

Book a call

See Zenik on your own repository.

The call takes 30 minutes. We show you the install screen, the workflow file, and a real pull request review. Use one of your own repositories.

Book a 30-minute call → No preparation is necessary