diff --git a/dist/index.js b/dist/index.js index 8f5b3873..6c1087e5 100644 --- a/dist/index.js +++ b/dist/index.js @@ -6677,9 +6677,9 @@ $raw_summary \`\`\` `; - summarizeShort = `Your task is to provide a concise summary of the changes -and the goal of this PR. This summary will be used as a prompt while reviewing each -file and must be very clear for the AI bot to understand. + summarizeShort = `Your task is to provide a concise summary of the changes. This +summary will be used as a prompt while reviewing each file and must be very clear for +the AI bot to understand. Instructions: @@ -6687,7 +6687,7 @@ Instructions: - Do not provide any instructions to the bot on how to perform the review. - Do not mention that files need a through review or caution about potential issues. - Do not mention that these changes affect the logic or functionality of the code. -- The summary should not exceed 250 words. +- The summary should not exceed 500 words. `; reviewFileDiff = `## GitHub PR Title @@ -6699,20 +6699,26 @@ Instructions: $description \`\`\` -## Summary generated by the AI bot +## Summary of changes \`\`\` $short_summary \`\`\` -## How to parse the changes +## Pseudo-code for \`$filename\` before changes + +\`\`\` +$file_summary +\`\`\` + +## Parsing changes The format for changes provided below consists of multiple change sections, each containing a new hunk (annotated with line numbers), an old hunk, and optionally, existing comment chains. Note that the -old hunk code has been replaced by the new hunk to fulfill the -goal of this PR. The line number annotation on each line in the new -hunk is of the format \`\`. +old hunk code has been replaced by the new hunk. The line number +annotation on each line in the new hunk is of the +format \`\`. ### Format for changes diff --git a/src/prompts.ts b/src/prompts.ts index df23be4a..1cd35b2e 100644 --- a/src/prompts.ts +++ b/src/prompts.ts @@ -66,9 +66,9 @@ $raw_summary ` - summarizeShort = `Your task is to provide a concise summary of the changes -and the goal of this PR. This summary will be used as a prompt while reviewing each -file and must be very clear for the AI bot to understand. + summarizeShort = `Your task is to provide a concise summary of the changes. This +summary will be used as a prompt while reviewing each file and must be very clear for +the AI bot to understand. Instructions: @@ -76,7 +76,7 @@ Instructions: - Do not provide any instructions to the bot on how to perform the review. - Do not mention that files need a through review or caution about potential issues. - Do not mention that these changes affect the logic or functionality of the code. -- The summary should not exceed 250 words. +- The summary should not exceed 500 words. ` reviewFileDiff = `## GitHub PR Title @@ -89,20 +89,26 @@ Instructions: $description \`\`\` -## Summary generated by the AI bot +## Summary of changes \`\`\` $short_summary \`\`\` -## How to parse the changes +## Pseudo-code for \`$filename\` before changes + +\`\`\` +$file_summary +\`\`\` + +## Parsing changes The format for changes provided below consists of multiple change sections, each containing a new hunk (annotated with line numbers), an old hunk, and optionally, existing comment chains. Note that the -old hunk code has been replaced by the new hunk to fulfill the -goal of this PR. The line number annotation on each line in the new -hunk is of the format \`\`. +old hunk code has been replaced by the new hunk. The line number +annotation on each line in the new hunk is of the +format \`\`. ### Format for changes