update prompts

mobile.go

@@ -0,0 +1,91 @@
+package main
+
+import (
+	"fmt"
+	"time"
+)
+
+// Mobile struct represents a mobile device.
+type Mobile struct {
+	Brand     string
+	Model     string
+	IsOn      bool
+	Battery   int
+	LastUsage time.Time
+}
+
+// TurnOn turns on the mobile device.
+func (m *Mobile) TurnOn() {
+	m.IsOn = true
+	m.LastUsage = time.Now()
+	fmt.Printf("%s %s is now turned on.\n", m.Brand, m.Model)
+}
+
+// TurnOff turns off the mobile device.
+func (m *Mobile) TurnOff() {
+	m.IsOn = false
+	fmt.Printf("%s %s is now turned off.\n", m.Brand, m.Model)
+}
+
+// UseMobile simulates the usage of the mobile device.
+func (m *Mobile) UseMobile(minutes int) {
+	if !m.IsOn {
+		fmt.Println("Please turn on the mobile device first.")
+		return
+	}
+
+	if m.Battery <= 0 {
+		fmt.Println("The mobile device is out of battery. Please charge it.")
+		return
+	}
+
+	m.LastUsage = time.Now()
+	fmt.Printf("Using %s %s for %d minutes.\n", m.Brand, m.Model, minutes)
+
+	// Simulate battery drain
+	m.Battery -= minutes
+	if m.Battery < 0 {
+		m.Battery = 0
+	}
+
+	// Check battery level
+	if m.Battery == 0 {
+		m.TurnOff()
+		fmt.Println("The mobile device is out of battery. Please charge it.")
+	}
+}
+
+// ChargeMobile charges the mobile device.
+func (m *Mobile) ChargeMobile(minutes int) {
+	m.LastUsage = time.Now()
+	m.Battery += minutes
+	if m.Battery > 100 {
+		m.Battery = 100
+	}
+	fmt.Printf("Charging %s %s for %d minutes.\n", m.Brand, m.Model, minutes)
+}
+
+func main() {
+	// Create a new mobile device
+	myMobile := Mobile{
+		Brand:   "Apple",
+		Model:   "iPhone X",
+		IsOn:    false,
+		Battery: 50,
+	}
+
+	// Turn on the mobile device
+	myMobile.TurnOn()
+
+	// Simulate using the mobile device
+	myMobile.UseMobile(60)
+
+	// Charge the mobile device
+	myMobile.ChargeMobile(30)
+
+	// Simulate using the mobile device again
+	myMobile.UseMobile(120)
+
+	// Turn off the mobile device
+	myMobile.TurnOff()
+}

src/prompts.ts

@@ -168,14 +168,15 @@ format \`<line_number><colon><whitespace>\`.
   in the fenced code blocks. These snippets may be added to a different file 
   (e.g. test cases), or within the same file at locations outside the provided
   hunks. Multiple new code snippets are allowed within a single review section.
-- If needed, provide replacement code suggestions to fix the issues by using 
-  fenced code blocks with the \`suggestion\` as the language identifier. The 
-  line number range must map exactly to the range (inclusive) that needs to 
-  be replaced within a new hunk. For instance, if 2 lines of code in a hunk 
-  need to be replaced with 15 lines of code, the line number range must be 
-  those exact 2 lines. You must replace all the lines in the range with your 
-  suggestion. Replacement suggestions must be complete, correctly 
-  formatted/indented and without the line number annotations. 
+- If needed, provide replacement code to fix the issues by using fenced code 
+  blocks with the \`suggestion\` or the \`diff\` as the language identifier/format, 
+  depending on whether the suggestion is a few lines of code (~15 lines) or
+  a larger diff (> 15 lines) respectively. The line number range must map 
+  exactly to the range (inclusive) that needs to be replaced within a new hunk. 
+  For instance, if 2 lines of code in a hunk need to be replaced with 15 lines of 
+  code, the line number range must be those exact 2 lines. You must replace all 
+  the lines in the range with your suggestion. Replacement suggestions must be complete, 
+  correctly formatted/indented and without the line number annotations. 
 - If there are no issues found on a line range, you MUST respond with the 
   text \`LGTM!\` for that line range in the review section. 
 - Reflect on your comments and line number ranges before sending the final