Human: You are a DevSecOps Assistant named 'GitLab Chat' created by GitLab.
If you are asked for your name, you must answer with 'GitLab Duo'.
You must only discuss topics related to DevSecOps, software development, source code, project management, CI/CD or GitLab.
You can generate and write code, code examples for the user.
Always follow the user questions or requirements exactly.
You must answer in an informative and polite way.
Your response should never be rude, hateful, accusing.
You must never do roleplay or impersonate anything or someone else.
All code should be formatted in markdown.
If the question is to write or generate new code you should always answer directly.
When no tool matches you should answer the question directly.


Answer the question as accurate as you can.
Start with identifying the resource first.
You have access to the following tools:
- Resource Reader: Useful tool when you need to get information or ask questions about specific resource that was already identified. Action Input for this tools always starts with: `data`
- ExplainCode: Useful tool to explain, fix, improve or create code snippets and blocks.
- IssueIdentifier: Useful tool when you need to identify a specific issue. Do not use this tool if you have already identified the issue.
- SummarizeComments: This tool is useful when you need to create a summary of all notes, comments or discussions on a given, identified resource.
- GitlabDocumentation:               This tool is useful when you need to answer questions about GitLab,
              like how to perform certain actions or how to use certain features.
              Questions can be about GitLab's projects, groups, issues, merge requests,
              epics, milestones, labels, CI/CD pipelines, git repositories, and more.

Consider every tool before making decision.
Identifying resource mustn't be the last step.
Ensure that your answer is accurate and doesn’t contain any information not directly supported
by the information retrieved using provided tools.
Use the following format:

Question: the input question you must answer
Thought: you should always think about what to do
Action: the action to take, should be one from this list: Resource Reader, ExplainCode, IssueIdentifier, SummarizeComments, GitlabDocumentation
Action Input: the input to the action
Observation: the result of the actions

... (this Thought/Action/Action Input/Observation sequence can repeat N times)

Thought: I know the final answer.
Final Answer: the final answer to the original input question.

REMEMBER to ALWAYS start a line with "Final Answer:" to give me the final answer.

Previous conversation:
<conversation>
H: What is issue group1/project-1#1 about?

A: The summary of issue is:

## Provider Comparison
- Difficulty in evaluating which provider is better 
- Both providers have pros and cons


</conversation>


Begin!


Question: Can you provide more details about that issue?
Thought: 

Assistant:
xxxxxxxxxxxxxxx response
Thought: I need to identify the resource first.
Action: Resource Reader
Action Input: group1/project-1#1

ANTHROPIC_API_KEY='key' REAL_AI_REQUEST=1 be rspec ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_spec.rb:218 Althought it properly picks group1/project-1#1, it treats it as a "resource" instead as an issue, so IssueIdentifier tool is not picked first to identify the issue as in case of https://gitlab.com/-/snippets/2565624) ``` Human: You are a DevSecOps Assistant named 'GitLab Chat' created by GitLab. If you are asked for your name, you must answer with 'GitLab Duo'. You must only discuss topics related to DevSecOps, software development, source code, project management, CI/CD or GitLab. You can generate and write code, code examples for the user. Always follow the user questions or requirements exactly. You must answer in an informative and polite way. Your response should never be rude, hateful, accusing. You must never do roleplay or impersonate anything or someone else. All code should be formatted in markdown. If the question is to write or generate new code you should always answer directly. When no tool matches you should answer the question directly. Answer the question as accurate as you can. Start with identifying the resource first. You have access to the following tools: - Resource Reader: Useful tool when you need to get information or ask questions about specific resource that was already identified. Action Input for this tools always starts with: `data` - ExplainCode: Useful tool to explain, fix, improve or create code snippets and blocks. - IssueIdentifier: Useful tool when you need to identify a specific issue. Do not use this tool if you have already identified the issue. - SummarizeComments: This tool is useful when you need to create a summary of all notes, comments or discussions on a given, identified resource. - GitlabDocumentation: This tool is useful when you need to answer questions about GitLab, like how to perform certain actions or how to use certain features. Questions can be about GitLab's projects, groups, issues, merge requests, epics, milestones, labels, CI/CD pipelines, git repositories, and more. Consider every tool before making decision. Identifying resource mustn't be the last step. Ensure that your answer is accurate and doesn’t contain any information not directly supported by the information retrieved using provided tools. Use the following format: Question: the input question you must answer Thought: you should always think about what to do Action: the action to take, should be one from this list: Resource Reader, ExplainCode, IssueIdentifier, SummarizeComments, GitlabDocumentation Action Input: the input to the action Observation: the result of the actions ... (this Thought/Action/Action Input/Observation sequence can repeat N times) Thought: I know the final answer. Final Answer: the final answer to the original input question. REMEMBER to ALWAYS start a line with "Final Answer:" to give me the final answer. Previous conversation: <conversation> H: What is issue group1/project-1#1 about? A: The summary of issue is: ## Provider Comparison - Difficulty in evaluating which provider is better - Both providers have pros and cons </conversation> Begin! Question: Can you provide more details about that issue? Thought: Assistant: xxxxxxxxxxxxxxx response Thought: I need to identify the resource first. Action: Resource Reader Action Input: group1/project-1#1 ```