GitLab Merge Request Review Agent with OpenCode
A review agent fails by inventing standards, objecting to a naming convention nobody agreed on or marking an item failed because it could not find the test file. This template forbids both: judgement comes from your checklist and the diff, and anything it cannot evidence is marked unclear with the reason stated. OpenCode is a comfortable home for that, since you pick the model and the checklist does the constraining.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Add idempotency keys to the refunds endpoint
Open@fatima.zahra
Adds an Idempotency-Key header to POST /refunds and stores the key against the refund for 24 hours, so a retried request returns the original refund instead of issuing a second one. Migration adds one table and a unique index. Twelve files, 340 lines added, 46 removed. Unit and integration tests included, pipeline green on the head commit. Closes issue 2841.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect GitLab
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Review checklist
What a merge request has to satisfy on this project in your own words, which of those items block a merge, and what you want asked of the author when an item cannot be judged from the diff alone.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
No opinions you did not write
Architecture preferences, coverage bars and style views that are absent from the checklist are not review comments. That rule holds whichever model sits behind it.
Visible tooling for engineers
Teams who care what is running inside their review loop tend to prefer an open, model agnostic harness over one they cannot inspect.
Before you fork
Does our source code leave the repository?
The parts it reads do. Diffs, commit messages and any file it opens for a checklist item go to the model you connect, so your choice of model provider is the real privacy decision here. NoClick does not train on it and nothing is stored in the repository beyond the note it posts. If a project cannot have its code read by an external model, do not point this at it.
Run it with a different agent
Put GitLab Merge Request Review Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.