try multi-line comments (#117)

Author: harjotgill

action.yml

@@ -98,9 +98,7 @@ inputs:
     required: false
     description: 'The prompt for the whole pull request'
     default: |
-      In this session, we will summarize a pull request and a diff alltogether. 
-
-      The pull request has the title "$title" and the following description:
+      GitHub pull request has the title "$title" and the following description:
 
       ```
       $description
@@ -151,7 +149,7 @@ inputs:
     required: false
     description: 'The prompt for each file'
     default: |
-      The pull request has the title "$title" and the following description:
+      GitHub pull request has the title "$title" and the following description:
 
       ```
       $description
@@ -172,29 +170,51 @@ inputs:
       Below is the format for diff patches. `---` 
       separator is used between patches. 
 
-      <line_number>: 
+      <start_line-end_line>: 
+      ```diff
+      <diff_hunk>
+      ```
       ```text
       <review comments on patch, if any>
       ```
-      ```diff
-      <patch>
-      ```
       ---
       ...
 
       Patches for review -
 
       $patches
 
-      Your review for each patch should be the following format 
-      with `---` separator between review comments. Make sure 
-      to use the line numbers exactly as provided above:
+      Your review must consist of comments in the following format 
+      with `---` separator between review comments. Any other 
+      commentary outside of this format will be ignored and will not 
+      be read by the parser. Your comments will be added as multi-line 
+      review comments in the GitHub pull request.
 
-      <line_number>:
-      <review>
+      <start_line-end_line>:
+      <review comment>
+      ---
+      <start_line-end_line>:
+      <explain why suggestion makes sense>
+      ```suggestion
+      <new code>
+      ```
       ---
       ...
 
+      You can comment or suggest code changes for any number 
+      of (sub) line ranges within the line ranges 
+      (start_line and end_line) as long as your line ranges are 
+      within the line ranges in the patches.
+      When suggesting code changes, the line ranges provided by you should 
+      map to exact line ranges that you wish to replace in the code 
+      with your new code suggestion. For example, if you are suggesting 
+      to replace 2 lines in code then the example comment could be -
+      100-101:
+      ```suggestion
+      print "Hello world"
+      end
+      ```
+
       Reflect on the provided code at least 3 times to identify any bug risks 
       or provide improvement suggestions in these patches. 
       You will point out potential issues such as security, logic errors, 
@@ -206,8 +226,7 @@ inputs:
       as-is, please include "LGTM!" (exact word) in your short 
       review comment.
 
-      Your responses will be recorded as review comments on the 
-      pull request. Markdown format is preferred for your responses.
+      Markdown format is preferred for your responses.
   comment:
     required: false
     description: 'Prompt for comment'
@@ -265,10 +284,6 @@ inputs:
       Please reply directly to the new comment (instead of suggesting 
       a reply) and your reply will be posted as-is.
 
-      If the comment contains instructions/requests for you, please comply. 
-      For example, if the comment is asking you to generate documentation 
-      comments on the code, in your reply please generate the required code.
-
       In your reply, please make sure to begin the reply by tagging the user 
       with "@user".
 
@@ -277,6 +292,17 @@ inputs:
       ```
       $comment
       ```
+
+      If the comment contains instructions/requests for you, please comply. 
+      For example, if the comment is asking you to generate documentation 
+      comments on the code, in your reply please generate the required code.
+      Any code change suggestion in the response must be enclosed in fenced code 
+      blocks with the suggestion identifier and must be in the line range
+      of diff hunk provided to you -
+      <your comment to the user>
+      ```suggestion
+      <change>
+      ```
 runs:
   using: 'node16'
   main: 'dist/index.js'