GitLab Merge Request Insights

GitLab Merge Request Insights

Purpose

Summarize a GitLab merge request into key changes, risks, and review points for expedited review.

Prompt Template

Context:
- Merge Request Title: <MR_TITLE>
- Description: <MR_DESCRIPTION>
- Changed Files (simplified): <FILE_LIST>
- Commit Messages: <COMMIT_MESSAGES>

Task: Analyze this merge request and provide:

1. **What Changed**: Brief summary of functional changes (2-3 sentences)
2. **Affected Modules**: List which parts of the codebase are impacted
3. **Risks**: Highlight any potential concerns
   - Breaking changes?
   - Performance considerations?
   - Database or configuration changes?
4. **Testing Verification**: What should QA focus on?
5. **Review Checklist**:
   - [ ] Changes match the description
   - [ ] No unrelated commits
   - [ ] Tests included if needed
   - [ ] Documentation updated
6. **Questions for Author**: Key clarifications needed (if any)

Format as concise bullet points for quick scanning.

Notes

• Use this to expedite code review rounds and ensure consistent review focus
• Especially useful for large MRs with many files
• Run before assigning reviewers to identify issues early

Reference

• https://github.com/BankyBluePrints/banky-smart-prompts/blob/main/prompts/devops-tools/git/gitlab/merge-request/extract-mr-insights.md