Modify the HI instructions to avoid using HI for testing

This commit is contained in:
Senko Rasic
2024-02-05 19:10:42 -08:00
parent 82f33204da
commit d43d030b91
5 changed files with 10 additions and 7 deletions

View File

@@ -1,6 +1,8 @@
**IMPORTANT**
You must not tell me to run a command in the database or anything OS related - only if some dependencies need to be installed. If there is a need to run an OS related command, specifically tell me that this should be labeled as "Human Intervention" and explain what the human needs to do.
Avoid using "Human Intervention" if possible. You should NOT use "Human Intervention" for anything else than steps that you can't execute. Here are few examples when and how to use "Human Intervention":
Avoid using "Human Intervention" if possible. You should NOT use "Human Intervention" for anything else than steps that you can't execute. Also, you must not use "Human Intervention" to ask user to test that the application works, because this will be done separately after all the steps are finished - no need to ask the user now.
Here are a few examples when and how to use "Human Intervention":
------------------------start_of_example_1---------------------------
Here is an example of good response for the situation where it seems like 3rd party API, in this case Facebook, is not working:

View File

@@ -15,7 +15,7 @@ Each step can be either:
* `command` - command to run (must be able to run on a {{ os }} machine, assume current working directory is project root folder)
* `code_change` - step will change the code and you need to thoroughly describe what needs to be implemented. I will implement the requested changes and let you know.
* `human_intervention` - if you need the human to do something, use this type of step and explain in details what you want the human to do.
* `human_intervention` - if you need the human to do something, use this type of step and explain in details what you want the human to do. NEVER use `human_intervention` for testing, as testing will be done separately by a dedicated QA after all the steps are done.
{{ execution_order }}

View File

@@ -5,7 +5,7 @@ Each step can be either:
* `command` - command to run (must be able to run on a {{ os }} machine, assume current working directory is project root folder)
* `save_file` - create a NEW file
* `modify_file` - update ONE EXISTING file
* `human_intervention` - if you need the human to do something, use this type of step and explain in details what you want the human to do.
* `human_intervention` - if you need the human to do something, use this type of step and explain in details what you want the human to do. NEVER use `human_intervention` for testing, as testing will be done separately by a dedicated QA after all the steps are done.
If the step is of type `save_file` or `modify_file`, it needs to contain instructions on how to change only ONE file.
@@ -15,6 +15,8 @@ If the step is of type `save_file` or `modify_file`, it needs to contain instruc
**IMPORTANT**: In `code_change_description` field of `modify_file` step, you must provide full information (including code samples, if any) from the previous message, so that the developer can correctly implement the change. For `save_file`, you MUST include FULL file contents, without omitting anything or adding comments like `// rest of the code goes here`.
**IMPORTANT**: Remember, NEVER output human intervention steps to do manual tests, even if the previous message asks for it! The testing will be done *after* these steps and you MUTS NOT include testing in these steps.
Examples:
------------------------example_1---------------------------
```

View File

@@ -1,7 +1,7 @@
[INST]I received an incomplete JSON response. Please provide the remainder of the JSON object. I will append your entire response to the incomplete JSON data below so it is important that you must not include any of the data already received or any text that does not complete the JSON data.
I received an incomplete JSON response. Please provide the remainder of the JSON object. I will append your entire response to the incomplete JSON data below so it is important that you must not include any of the data already received or any text that does not complete the JSON data.
A response which starts with "Here is the remainder of the JSON object" would be an example of an invalid response, a preamble must NOT be included.
Note that because the JSON data I have already received is an incomplete JSON object, you will not need to include the opening and closing curly braces in your response, but rather continue off from EXACTLY where the received JSON ends.
JSON received:
[/INST]
{{ received_json }}

View File

@@ -1,6 +1,5 @@
[INST]I received an invalid JSON response. The response was a parseable JSON object, but it is not valid against the schema I provided. The JSON is invalid {{ invalid_reason }}
I received an invalid JSON response. The response was a parseable JSON object, but it is not valid against the schema I provided. The JSON is invalid {{ invalid_reason }}
Please try again with a valid JSON object, referring to the previous JSON schema I provided above.
A response which starts with "I'm sorry for the confusion" would be an example of an invalid response, a preamble must NOT be included.
[/INST]