Auto code review on every merge request — with task context

For every merge request the scenario reviews the code changes, checks them against the Jira Software task and leaves comments right on the request.

  • Reviews every request on its own
  • Uses the task description from the tracker
  • Comments are tied to the lines
  • Frees reviewers on the first pass
Jira SoftwareWebhookGitLab
Set it upMade with Scriptera

How it works

To connect Jira Software and Webhook, you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: Error Trigger
  2. Then: Get Static Context Including Error
  3. Then: Post Error Occurred
  4. Then: Cleanup Static Context
  5. Check: Need Review
  6. If yes: Set workflow execution information
  7. Then: Post Review Started
  8. Then: Extract MR Details
  9. Then: Get MR Changes
  10. Check: Merge
  11. Then: Split Out Changes
  12. Check: Skip File Changes
  13. If yes: Parse Diff
  14. Then: Prepare Code Changes
  15. Then: Basic LLM Chain
  16. Check: Merge LLM Output with Input
  17. Then: Aggregate
  18. Then: Process Comments
  19. Check: Any Issues Found?
  20. If yes: Get Static Context
  21. Then: Post No Issues Found
  22. If no: Split Out Comments
  23. Then: Prepare Request
  24. Then: Post Gitlab MR Comments
  25. Then: Prepare Request Without Position
  26. Then: Post Gitlab MR Comments WIthout Position
  27. Then: Filter Irrelevant Fields
  28. Then: Extract the JIRA Issue ID
  29. Then: Get JIRA issue
  30. Then: Format JIRA Context
  31. Check: If JIRA Subtask
  32. If yes: Get JIRA Parent Issue
  33. Then: Format JIRA Parent Context
  34. Then: Google Gemini Chat Model
  35. Starts when: Listen For Gitlab Comments

You can launch this Jira Software + Webhook integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios