• Ask about GitLab
• Ask about code
• Ask about CI/CD
• Troubleshoot failed CI/CD jobs with root cause analysis
• Explain a vulnerability
• Explain code in the IDE
• Refactor code in the IDE
• Fix code in the IDE
• Write tests in the IDE
• Ask about errors
• Ask follow up questions
• Ask about a specific issue
• Ask about a specific epic
• Delete or reset the conversation
• Supported slash commands

Ask GitLab Duo Chat

GitLab Duo Chat can help with a variety of questions. The following examples represent some of the areas where GitLab Duo Chat can be the most helpful.

For additional practical examples, see the GitLab Duo use cases.

Ask about GitLab

You can ask questions about how GitLab works. Things like:

• Explain the concept of a 'fork' in a concise manner.
• Provide step-by-step instructions on how to reset a user's password.

Ask about code

You can also ask GitLab Duo Chat to generate code:

• Write a Ruby function that prints 'Hello, World!' when called.
• Develop a JavaScript program that simulates a two-player Tic-Tac-Toe game. Provide both game logic and user interface, if applicable.
• Create a regular expression for parsing IPv4 and IPv6 addresses in Python.
• Generate code for parsing a syslog log file in Java. Use regular expressions when possible, and store the results in a hash map.
• Create a product-consumer example with threads and shared memory in C++. Use atomic locks when possible.
• Generate Rust code for high performance gRPC calls. Provide a source code example for a server and client.

And you can ask GitLab Duo Chat to explain code:

• Provide a clear explanation of the given Ruby code: def sum(a, b) a + b end. Describe what this code does and how it works.

Alternatively, you can use the /explain command to explain the selected code in your editor.

Ask about CI/CD

You can ask GitLab Duo Chat to create a CI/CD configuration:

• Create a .gitlab-ci.yml configuration file for testing and building a Ruby on Rails application in a GitLab CI/CD pipeline.
• Create a CI/CD configuration for building and linting a Python application.
• Create a CI/CD configuration to build and test Rust code.
• Create a CI/CD configuration for C++. Use gcc as compiler, and cmake as build tool.
• Create a CI/CD configuration for VueJS. Use npm, and add SAST security scanning.
• Generate a security scanning pipeline configuration, optimized for Java.

You can also ask to explain specific job errors by copy-pasting the error message, prefixed with Please explain this CI/CD job error message, in the context of <language>::

• Please explain this CI/CD job error message in the context of a Go project: build.sh: line 14: go command not found

Alternatively, you can use root cause analysis to troubleshoot failed CI/CD jobs.

Troubleshoot failed CI/CD jobs with root cause analysis

You can ask GitLab Duo Chat to determine the root cause of a CI/CD job failure by analyzing the logs.

Prerequisites:

• Have permission to view the CI/CD job.
• Have a paid GitLab Duo Enterprise seat.

To troubleshoot a failed CI/CD job:

1. On the left sidebar, select Search or go to and find your project.
2. Select Build > Jobs.
3. Select the failed CI/CD job.

4. From the job log page, do one of the following:

   • Above the job log, select Troubleshoot.
   • Open GitLab Duo Chat and type /troubleshoot.

An analysis of the reasons for the failure and an example fix is displayed.

Explain a vulnerability

/vulnerability_explain is a special command you can use when you are viewing a SAST vulnerability report.

Learn more.

Explain code in the IDE

/explain is a special command to explain the selected code in your editor. You can also add additional instructions to be considered, for example: /explain the performance See Use GitLab Duo Chat in VS Code for more information.

• /explain focus on the algorithm
• /explain the performance gains or losses using this code
• /explain the object inheritance (classes, object-oriented)
• /explain why a static variable is used here (C++)
• /explain how this function would cause a segmentation fault (C)
• /explain how concurrency works in this context (Go)
• /explain how the request reaches the client (REST API, database)

You can also use the Web UI to explain code in:

• A file.
• A merge request.

Refactor code in the IDE

/refactor is a special command to generate a refactoring suggestion for the selected code in your editor. You can include additional instructions to be considered. For example:

• Use a specific coding pattern, for example /refactor with ActiveRecord or /refactor into a class providing static functions.
• Use a specific library, for example /refactor using mysql.
• Use a specific function/algorithm, for example /refactor into a stringstream with multiple lines in C++.
• Refactor to a different programming language, for example /refactor to TypeScript.
• Focus on performance, for example /refactor improving performance.
• Focus on potential vulnerabilities, for example /refactor avoiding memory leaks and exploits.

Fix code in the IDE

/fix is a special command to generate a fix suggestion for the selected code in your editor. You can include additional instructions to be considered. For example:

• Focus on grammar and typos, for example, /fix grammar mistakes and typos.
• Focus on a concrete algorithm or problem description, for example, /fix duplicate database inserts or /fix race conditions.
• Focus on potential bugs that are not directly visible, for example, /fix potential bugs.
• Focus on code performance problems, for example, /fix performance problems.
• Focus on fixing the build when the code does not compile, for example, /fix the build.

Write tests in the IDE

/tests is a special command to generate a testing suggestion for the selected code in your editor. You can also add additional instructions to be considered, for example: /tests using the Boost.Test framework See Use GitLab Duo Chat in VS Code for more information.

• Use a specific test framework, for example /tests using the Boost.test framework (C++) or /tests using Jest (JavaScript).
• Focus on extreme test cases, for example /tests focus on extreme cases, force regression testing.
• Focus on performance, for example /tests focus on performance.
• Focus on regressions and potential exploits, for example /tests focus on regressions and potential exploits.

Ask about errors

Programming languages that require compiling the source code may throw cryptic error messages. Similarly, a script or a web application could throw a stack trace. You can ask GitLab Duo Chat by prefixing the copied error message with, for example, Please explain this error message:. Add the specific context, like the programming language.

• Explain this error message in Java: Int and system cannot be resolved to a type
• Explain when this C function would cause a segmentation fault: sqlite3_prepare_v2()
• Explain what would cause this error in Python: ValueError: invalid literal for int()
• Why is "this" undefined in VueJS? Provide common error cases, and explain how to avoid them.
• How to debug a Ruby on Rails stacktrace? Share common strategies and an example exception.

Ask follow up questions

You can ask follow-up questions to delve deeper into the topic or task at hand. This helps you get more detailed and precise responses tailored to your specific needs, whether it’s for further clarification, elaboration, or additional assistance.

A follow-up to the question Write a Ruby function that prints 'Hello, World!' when called could be:

• Can you also explain how I can call and execute this Ruby function in a typical Ruby environment, such as the command line?

A follow-up to the question How to start a C# project? could be:

• Can you also please explain how to add a .gitignore and .gitlab-ci.yml file for C#?

Ask about a specific issue

You can ask about a specific GitLab issue. For example:

• Generate a summary for the issue identified via this link: <link to your issue>
• When you are viewing an issue in GitLab, you can ask Generate a concise summary of the current issue.
• How can I improve the description of <link to your issue> so that readers understand the value and problems to be solved?

For tips on how GitLab Duo Chat can improve your productivity with issues and epics, see Boost your productivity with GitLab Duo Chat.

Ask about a specific epic

You can ask about a specific GitLab epic. For example:

• Generate a summary for the epic identified via this link: <link to your epic>
• When you are viewing an epic in GitLab, you can ask Generate a concise summary of the opened epic.
• What are the unique use cases raised by commenters in <link to your epic>?

Delete or reset the conversation

To delete all conversations permanently and clear the chat window:

• In the text box, type /clear and select Send.

To start a new conversation, but keep the previous conversations visible in the chat window:

• In the text box, type /reset and select Send.

In both cases, the conversation history will not be considered when you ask new questions. Deleting or resetting might help improve the answers when you switch contexts, because Duo Chat will not get confused by the unrelated conversations.

Supported slash commands

Duo Chat has a list of supported commands, each of which is preceded by a slash (/). Use the following commands to quickly accomplish specific tasks.