allow it to be wider acceptable in the audit, don't be so strict

This commit is contained in:
2025-05-07 04:01:23 -03:00
parent 70b10d32bf
commit b79ee822e1

View File

@ -7,8 +7,8 @@ PROMPTS = {
"and creating clear, structured documentation."
),
"check_readme_file": (
"A pull request has been checked out for you. Review the file README_Prometheus.md in the repository "
"and evaluate its quality and relevance to the repository.\n\n"
"Review the README_Prometheus.md in the repository and evaluate its quality and "
"relevance to the repository.\n\n"
"Please analyze:\n"
"1. Is the README_Prometheus.md file related to this specific repository? (Does it describe the actual code "
"and purpose of this repo?)\n"
@ -16,7 +16,7 @@ PROMPTS = {
"3. Is it comprehensive enough to help users understand and use the repository?\n"
"4. Does it follow best practices for README documentation?\n\n"
"Use the `review_readme_file` tool to submit your findings.\n"
"IMPORTANT: Do not assume that an existing README is correct. "
# "IMPORTANT: Do not assume that an existing README is correct. "
"Evaluate README_Prometheus.md against the codebase.\n"
"DO NOT consider the filename in your analysis, only the content.\n"
"STOP after submitting the review report."