Roast the slop.
Before it merges.
Your preview deploy landed at 3 am with seven gradients and a hero that says “Welcome to the future.” Drop one script tag, click what hurts, leave pinned comments, and submit straight into a GitLab merge request — labels, pipelines, approve, merge.
How it works
From preview slop to merged
Same flow your team already knows — except the feedback is pinned on the actual page, not lost in a MR thread nobody reads.
What you get
Everything reviewers need.
Nothing your CSS didn’t ask for.
One <script> on any preview HTML page. Toolbar UI stays in shadow DOM; comment pins anchor to elements in your page.
Draft comments locally, submit to the MR, poll pipeline status, approve or merge from the dock. Push layout on wide screens; overlay on mobile.
Register repos via GitLab OAuth or a PAT. Encrypted tokens in SQLite, CI setup snippets, project secrets, and shareable review links per MR.
Tracks changing → ready → approved on the merge request so humans (and CI) know when the slop is done cooking.
Try it now
Real pages, not marketing fiction
Mock preview site with the toolbar loaded. Pin comments, draft locally, see the panel — no GitLab account required to poke it.
Sign up, connect GitLab, register a project, copy CI variables, generate review links. This is where slop gets a project ID.
Checking /health…
Still merging unreviewed slop?
Self-host the API, register your first project, and embed on the next preview that definitely wasn’t hand-crafted.