update prompt (#405)

<!-- This is an auto-generated comment: release notes by OSS CodeRabbit
-->
### Summary by CodeRabbit

```
- **New Feature**: Added `Mobile` struct in `mobile.go` to simulate a mobile device's operations.
- **Refactor**: Updated `format_error` function in `src/prompts.ts` to include line numbers in error messages for better debugging.

```

> 🎉 With every line of code, we strive,
>
> In `mobile.go`, a new `Mobile` comes alive! 📱
>
> And in `prompts.ts`, no more guess and dive,
>
> For `format_error` now tells where the issue lies! 🐞🔍

<!-- end of auto-generated comment: release notes by OSS CodeRabbit -->

Author: harjotgill

dist/index.js

@@ -141,13 +141,21 @@ format \`<line_number><colon><whitespace>\`.
   references to elements defined outside the provided context. Do not 
   flag issues about missing definitions, imports, or uses unless there is 
   strong evidence within the provided context to suggest there might be a problem.
-  Do not repeat information that is already evident from the code or the pull
+- Do not repeat information that is already evident from the code or the pull
   request. Do not include general feedback, summaries, explanations of changes, 
-  compliments for following good practices. Do not question the developer's 
-  intention behind the changes or caution them to ensure that their modifications 
-  do not introduce compatibility issues with other dependencies. Do not make 
-  presumptions about the larger impact outside the given context or the necessity 
-  of the changes. Do not ask the developer to review the changes.
+  compliments for following good practices. 
+- Do not question the developer's intention behind the changes or caution them to 
+  ensure that their modifications do not introduce compatibility issues with 
+  other dependencies. 
+- Do not make presumptions about the larger impact outside the given context or 
+  the necessity of the changes. 
+- Do not ask the developer to review the changes.
+- As your knowledge may be outdated, trust the developer when newer
+  APIs and methods are seemingly being used.
+- Always presume that the developer has thoroughly tested their changes 
+  and is aware of their implications on the entire system. Instead of 
+  making generic comments about potential impacts on the system, focus 
+  on providing specific, objective insights based on the code itself. 
 - Respond only in the below response format (consisting of review 
   sections). Each review section must have a line number range and a review 
   comment for that range. Use separator after each review section.
@@ -169,12 +177,6 @@ format \`<line_number><colon><whitespace>\`.
   then the line number range must be the entire hunk and the new code must
   exactly replace ALL the lines in the hunk. Replacement suggestions should be 
   complete, correctly formatted and without the line number annotations. 
-- As your knowledge may be outdated, trust the developer when newer
-  APIs and methods are seemingly being used.
-- Always presume that the developer has thoroughly tested their changes 
-  and is aware of their implications on the entire system. Instead of 
-  making generic comments about potential impacts on the system, focus 
-  on providing specific, objective insights based on the code itself. 
 - 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 
@@ -204,6 +206,7 @@ format \`<line_number><colon><whitespace>\`.
 ### Example changes
 
   ---new_hunk---
+  \`\`\`
   12:     z = x / y
   13:     return z
   14: 
@@ -216,8 +219,10 @@ format \`<line_number><colon><whitespace>\`.
   21: 
   22: def subtract(x, y):
   23:     z = x - y
+  \`\`\`
   
   ---old_hunk---
+  \`\`\`
       z = x / y
       return z
 
@@ -226,6 +231,7 @@ format \`<line_number><colon><whitespace>\`.
   
   def subtract(x, y):
       z = x - y
+  \`\`\`
 
   ---end_change_section---