1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
---
stage: AI-powered
group: Duo Chat
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# GitLab Duo Chat best practices
When prompting GitLab Duo Chat with questions, keep the following best practices in mind.
## Have a conversation
Treat chats like conversations, not search forms. Start with a search-like question,
then follow up with related questions to refine the scope. Build context through back-and-forth.
For example, you might ask:
```plaintext
c# start project best practices
```
Then follow up with:
```plaintext
Please show the project structure for the C# project.
```
## Refine the prompt
For better responses, provide more context up front.
Think through the full scope of what you need help with and include it in one prompt.
```plaintext
How can I get started creating an empty C# console application in VS Code?
Please show a .gitignore and .gitlab-ci.yml configuration with steps for C#,
and add security scanning for GitLab.
```
## Follow prompt patterns
Structure prompts as problem statement, request for help, then add specificity.
Don't feel you must ask everything up front.
```plaintext
I need to fulfill compliance requirements. How can I get started with Codeowners and approval rules?
```
Then ask:
```plaintext
Please show an example for Codeowners with different teams: backend, frontend, release managers.
```
## Use low-context communication
Even if code is selected, provide context as if none is visible.
Be specific on factors like language, framework, and requirements.
```plaintext
When implementing a pure virtual function in an inherited C++ class,
should I use virtual function override, or just function override?
```
## Repeat yourself
Try rephrasing a question if you get an unexpected or strange response. Add more context.
```plaintext
How can I get started creating an C# application in VS Code?
```
Follow up with:
```plaintext
How can I get started creating an empty C# console application in VS Code?
```
## Be patient
Avoid yes/no questions. Start general, then provide specifics as needed.
```plaintext
Explain labels in GitLab. Provide an example for efficient usage with issue boards.
```
## Reset when needed
Use `/reset` if Chat gets stuck on a wrong track. Start fresh.
## Refine slash command prompts
Go beyond the basic slash command. Use them with more specific suggestions.
```plaintext
/refactor into a multi-line written string. Show different approaches for all C++ standards.
```
Or:
```plaintext
/explain why this code has multiple vulnerabilities
```
## Related topics
- Duo Chat best practices [blog post](https://about.gitlab.com/blog/2024/04/02/10-best-practices-for-using-ai-powered-gitlab-duo-chat/)
- [Videos on how to use Chat](https://www.youtube.com/playlist?list=PL05JrBw4t0Kp5uj_JgQiSvHw1jQu0mSVZ)
- [Request a Duo Chat learning session](https://gitlab.com/groups/gitlab-com/marketing/developer-relations/-/epics/476)
|
