[Feedback] Add more GitLab-centric Automations + Refine Automation Template UX

GitLab-Centric Automation Templates

Overview

Expand automation templates beyond GitHub with a GitLab-focused set for common software-delivery workflows.

Problem

Current templates are GitHub-centric. GitLab users need equivalent automations for code review, work items, and requirements refinement.

Goals

• Provide GitLab-native automation templates.
• Support workflows from issue/work item through merge request.
• Improve work-item quality before engineering begins.

Initial Templates

1. Code Review Automation

Modeled after the GitHub code review automation, this would be modified to support GitLab-centric concepts like Merge Requests.

2. Work Item to Merge Request Automation

Modeled after the GitHub Issue to PR automation, this would be modified to support GitLab-centric concepts like Work Items and Merge Requests.

• PR: #525

3. PRD Refiner

This would be a new Automation designed for Product Manager personas. It would analyze a GitLab work item and post a comment containing:

• Open questions
• Recommendations
• Gaps or ambiguities in the user story

Optionally, the automation can analyze the linked repository/codebase when repository hints appear in the work-item description or comments. This should add implementation-aware context to the refinement feedback.

• Verify the automations should up under Automations > Templates
• Verify the Automations > Templates allow for filtering by integration (e.g., GitHub, GitLab, Jira, etc.)

Start by reviewing the existing GitHub code review and Issue-to-PR automations, then inspect Automations > Templates. Define the GitLab-focused templates and integration filtering described in the issue; done means the templates appear there and filtering by integrations can be verified.