GitLab Merge Request Review Agent with Hermes
Reviews are worth paying for while the change is still in the author's head, and this template fires on open, reopen and update while ignoring the issues, comments, tags and pipeline events sharing the same stream. Run count therefore tracks review activity and nothing else. Hermes does the job hosted, with GitLab and Slack wired in as tools and open weights underneath.
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 Hermes
Preselected for this page — connect your Hermes 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 Hermes for this agent
Most events cost nothing
Anything that is not a qualifying merge request event stops immediately, with no note, no Slack line and no output at all.
Your engineers judge the verdicts
The audience for every note is your own reviewers, who are better placed than anyone to say whether an open model's checklist calls are worth keeping.
Before you fork
Is the note there before a reviewer opens the merge request?
Usually. The run starts on the event and spends most of its time gathering the diff, the commits and the pipeline, so a note on a normal change lands within a minute or two. A very large merge request takes longer, and if the pipeline is still running the note says so rather than waiting for it to finish.
Run it with a different agent
Put GitLab Merge Request Review Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.