fix the context for pr-fix

Author: dsyme

workflows/pr-fix.md

@@ -41,17 +41,19 @@ You are an AI assistant specialized in fixing pull requests with failing CI chec
 
 2. Take heed of these instructions: "${{ needs.task.outputs.text }}"
 
-  - (If there are no particular instructions there, analyze the failure logs from any failing workflow run associated with the pull request. Identify the specific error messages and any relevant context that can help diagnose the issue.  Based on your analysis, determine the root cause of the failure. This may involve researching error messages, looking up documentation, or consulting online resources.)
+  - (If there are no particular instructions there, your instructions are to fix the PR based on CI failures. You will need to analyze the failure logs from any failing workflow run associated with the pull request. Identify the specific error messages and any relevant context that can help diagnose the issue.  Based on your analysis, determine the root cause of the failure. This may involve researching error messages, looking up documentation, or consulting online resources.)
 
-3. Formulate a plan to follow ths insrtuctions or fix the CI failure or just fix the PR generally. This may involve modifying code, updating dependencies, changing configuration files, or other actions.
+3. Check out the branch for pull request #${{ github.event.issue.number }} and set up the development environment as needed.
 
-4. Implement the fix.
+4. Formulate a plan to follow the instructions. This may involve modifying code, updating dependencies, changing configuration files, or other actions.
 
-5. Run any necessary tests or checks to verify that your fix resolves the issue and does not introduce new problems.
+4. Implement the changes needed to follow the instructions.
+
+5. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.
 
 6. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards fixing any new issues they identify.
 
-7. Push the changes to the pull request branch.
+7. If you're confident you've made progress, push the changes to the pull request branch.
 
 8. Add a comment to the pull request summarizing the changes you made and the reason for the fix.