AI Prompts

A library of useful prompts for Duo and other AI tools used by our team

Support Rotation Handover Prompt

Here is a prompt than can be used in Duo Agentic mode to summarise the work on an issue which has not yet been closed, in order to hand it over to another engineer. Execute this prompt and you can copy the response into the handover notes when another colleague begins their support rotation:

Prompt text

Please concisely summarize the current status of this issue, in order to hand it
over to the next backend engineer on customer support rotation duty for the
Groups & Projects team.

Use this template:

---

A handover comment generated by Duo and reviewed by me:

### Current status

<!-- Content of current status -->

*Confidence: <!-- Percentage confidence level in the accuracy of this status -->*

### Action items

- <!-- GitLab handle of DRI --> (*Confidence: <!-- Percentage confidence in who should be DRI for this item -->*): <!-- Action item -->. (*Confidence: <!-- Percentage confidence in the validity of this action item -->*)

---

- Be sure, or be conservative.
- When making assertions, be wary of hallucinations.
- Use qualifying language as appropriate.
- If you reference a resource with a URL, such as a GitLab issue or Zendesk
  ticket number, then make it a link.
- Read linked URLs if the added context might improve your answer.
- Answer with only Markdown code. I will review it and post it.
Example output

A handover comment generated by Duo and reviewed by me:

Current status

This is a regression in GitLab 18.3 where the last_repository_check_failed URL parameter filter is not working in the admin projects page. The issue was identified as being caused by the admin_projects_vue feature flag migration - when the flag is enabled, the parameter is ignored and all projects are returned instead of filtering for projects with failed repository checks.

@smaglangit has taken ownership of this issue and is actively working on a fix. The issue is currently in workflow::in dev status and has been linked to #561340 (the feature flag cleanup issue) as a blocking dependency. Multiple merge requests have been referenced (!203618, !203621, !204306) indicating active development work.

The issue affects customers on GitLab 18.3.1 and has been reproduced on v18.3. It’s scheduled for the 18.4 milestone (release date: September 18, 2025) with only 2 days remaining until code cutoff.

Confidence: 95%

Action items

  • @smaglangit (Confidence: 100%): Complete the fix for the last_repository_check_failed filter regression as part of the admin_projects_vue feature flag migration work. (Confidence: 95%)
  • @smaglangit (Confidence: 90%): Ensure the fix is included in the 18.4 milestone given the tight timeline (code cutoff in 2 days). (Confidence: 85%)

Request For Support Issue Triage

This prompt can help summarise what could be causing an issue and find good starter questions to ask a customer before further development can happen:

Prompt text

Investigate this issue, read the feature docs, suggest possible root causes and
questions to ask the customer.

Identify if any other issues in the `request-for-help` project could be related.
Example output

Epic Summary Prompt

This prompt can be used to ask Duo to look at an individual epic and summarise the most recent changes and blockers in the last week. Use it to formulate a weekly status update message which is readable and easy to dig into for links.

Prompt text

Generate a status update for this Epic using the following format.
The "Achievements" section should highlight any issues closed within the last 7
days since the last status update, with a short (1-2 sentence) summary of what
the issue accomplishes for customers. "Blockers" can be either left empty,
or use any issues whose status is blocked. For the "Next" section, include any
issues that have an assignee and have the status "in dev" or "in review".

---

## <!-- Date in YYYY-MM-DD --> – <!-- Title of Epic -->

<!-- Create a high level summary -->

### :tada: **Achievements**:

- <!-- Content of Achievements -->

### :issue-blocked: **Blockers**:

- <!-- Content of Blockers (optional) -->

### :arrow_forward: **Next**:

- <!-- Content of Next -->

---

- Be sure, or be conservative.
- When making assertions, be wary of hallucinations.
- Use qualifying language as appropriate.
- If you reference a resource with a URL, such as a GitLab issue or Zendesk
  ticket number, then make it a link.
- Read linked URLs if the added context might improve your answer.
- Answer with only Markdown code. I will review it and post it.
- Format the summary in a conversational, readable manner. Avoid business speak.
- You should use markdown for the output and wrap it in backticks.
Example output

2025-09-10 – Organization backend essentials

The team continues working on the final cleanup tasks to complete the Organization backend essentials. All remaining issues are actively being developed and are targeted for the 18.4 milestone.

🎉 Achievements

  • No issues were completed since the last status update on 2025-09-08

:issue-blocked: Blockers

  • N/A

▶️ Next

Last modified September 12, 2025: Document Organizations team AI prompts (fbf67f21)
View page source - Edit this page - please contribute. Creative Commons License