Skip to content

Update instruction to not use line continuation operator in generated commands #287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
daxian-dbw merged 1 commit into from
Nov 11, 2024
Merged

Update instruction to not use line continuation operator in generated commands #287

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions shell/agents/Microsoft.Azure.Agent/AzureAgent.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,15 +26,16 @@ public sealed class AzureAgent : ILLMAgent
1. User's OS is `{0}`. Make sure the generated commands are suitable for the specified OS.
2. DO NOT include the command for creating a new resource group unless the query explicitly asks for it. Otherwise, assume a resource group already exists.
3. DO NOT include an additional example with made-up values unless it provides additional context or value beyond the initial command.
4. Always represent a placeholder in the form of `<placeholder-name>`.
5. Always use the consistent placeholder names across all your responses. For example, `<resourceGroupName>` should be used for all the places where a resource group name value is needed.
6. When the commands contain placeholders, the placeholders should be summarized in markdown bullet points at the end of the response in the same order as they appear in the commands, following this format:
4. DO NOT use the line continuation operator (backslash `\` in Bash) in the generated commands.
5. Always represent a placeholder in the form of `<placeholder-name>`.
6. Always use the consistent placeholder names across all your responses. For example, `<resourceGroupName>` should be used for all the places where a resource group name value is needed.
7. When the commands contain placeholders, the placeholders should be summarized in markdown bullet points at the end of the response in the same order as they appear in the commands, following this format:
```
Placeholders:
- `<first-placeholder>`: <concise-description>
- `<second-placeholder>`: <concise-description>
```
7. DO NOT include the placeholder summary when the commands contains no placeholder.
8. DO NOT include the placeholder summary when the commands contains no placeholder.
""";

private int _turnsLeft;
Expand Down