GitLab Duo Chat best practices

When prompting GitLab Duo Chat with questions, apply the following best practices to receive concrete examples and specific guidance.

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:

c# start project best practices

Then follow up with:

Please show the project structure for the C# project.

With GitLab Duo Chat (Agentic), you can have a conversation that includes multiple projects.

Tell me the difference between project A and project B.

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.

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.

Or, with GitLab Duo Chat (Agentic):

Create an empty C# console application.
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.

I need to fulfill compliance requirements. How can I get started with Codeowners and approval rules?

Then ask:

Please show an example for Codeowners with different teams: backend, frontend, release managers.

Or, with GitLab Duo Chat (Agentic):

Create Codeowners with different teams: backend, frontend, release managers.

The group names are "backend-dev," "frontend-dev," and "release-man."

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.

When implementing a pure virtual function in an inherited C++ class,
should I use virtual function override, or just function override?

This context is less important when you use GitLab Duo Chat (Agentic) because it autonomously searches, retrieves, and combines information from multiple sources. However, you should still be explicit to help Chat work as efficiently as possible.

Repeat yourself

Try rephrasing a question if you get an unexpected or strange response. Add more context.

How can I get started creating an C# application in VS Code?

Follow up with:

How can I get started creating an empty C# console application in VS Code?

Or, with GitLab Duo Chat (Agentic):

Create an empty C# console application in my test project.

Be patient

Avoid yes/no questions. Start general, then provide specifics as needed.

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.

Refine slash command prompts

Go beyond the basic slash command. Use slash commands with more specific suggestions.

/refactor into a multi-line written string. Show different approaches for all C++ standards.

Or:

/explain why this code has multiple vulnerabilities

Although slash commands still work for GitLab Duo Chat (Agentic), they are not as critical as they are in GitLab Duo Chat (Classic). You can ask Chat to explain or refactor code and it can search across projects, create and edit files, and analyze information from multiple sources simultaneously.