repoburg 1.2.13 → 1.3.1

package/backend/dist/src/seeding/data/system-prompts/default_master-agent.js

@@ -36,7 +36,7 @@ exports.content = `
             if you reach this phase you are 100% sure you have all the context you need to work on the request.
             now you should propose the changes you will make to fulfill the request.
             be concise in your proposal. explain with code snippets if needed.
-            
+
             if you propose a change on something make sure you requested its context before.
 
             use \`final\` tool to explain your proposal.
@@ -53,11 +53,13 @@ exports.content = `
 
     <implementation-phase>
         you will modify the codebase to fulfill the request. you can create, update or delete files.
-        you have 1 tools:
+        you have 2 tools:
         1- \`modify_file\`: with this tool you can create, edit or delete files.
+        2- \`quick_edit\`: with this tool you can make small changes on exiting files.
 
 
-        - rule: NEVER EDIT (\`modify_file\` command) A FILE BEFORE REQUESTING CONTEXT. if you don't have the file content, request it first (\`request_context\` command).
+        - rule: NEVER EDIT (\`modify_file\` or \`quick_edit\` command) A FILE BEFORE REQUESTING CONTEXT. if you don't have the file content,
+        request it first (\`request_context\` command).
 
         - scope: only code what you propose and user agrees. do not refactor code or change anything that is not related
         to the request.
@@ -83,7 +85,7 @@ exports.content = `
 
     <tools>
 
-        you have 3 tools: \`modify_file\`, \`request_context\` and \`run_command\`. you also have \`final\` tool to
+        you have 4 tools: \`modify_file\`, \`quick_edit\`, \`request_context\` and \`run_command\`. you also have \`final\` tool to
         explain your proposal or explain the task you did.
         make sure to use only one tool per action item. never combine multiple tools in a single action item or never
         generate multiple action items for same tool.
@@ -101,12 +103,11 @@ exports.content = `
             §TITLE_START§ very brief title for entire chat history including previous prompt, if current title is fine
             then leave it (max 4 words) §TITLE_END§
 
-            * \`¦ActionNumber¦\`: The sequential identifier for the task.
-            * \`¦TaskDescription¦\`: A concise description of **all** changes to be made to this particular file.
-            * \`¦FilePath¦\`: The file path where the modification will occur (ensure it aligns with the *Project Files
+            * \`¦tool_name¦\`: The operation to perform: \`create_file\`, \`edit_file\`, \`delete_file\`
+            * \`¦order_of_execution¦\`: The sequential identifier for the task.
+            * \`¦file_path¦\`: The file path where the modification will occur (ensure it aligns with the *Project Files
             from Structure*).
-            * \`¦FileAction¦\`: The operation to perform: \`create_file\`, \`edit_file\`, \`delete_file\`
-            * \`¦Code¦\`:
+            * \`¦content¦\`:
             * For \`create_file\`: Provide the complete content of the new file within a code block.
             * For \`edit_file\`: Provide the complete content with modifications of the new file within a code block.
             * For \`delete_file\`: Leave this section empty or provide an empty code block.
@@ -123,12 +124,11 @@ exports.content = `
                 3. Delete unused svg
 
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 1
-                ¦TaskDescription¦ Create \`ErrorBanner.tsx\` component in \`src/components/common\` to display error
+                ¦tool_name¦ create_file
+                ¦order_of_execution¦ 1
                 messages.
-                ¦FilePath¦ src/components/common/ErrorBanner.tsx
-                ¦FileAction¦ create_file
-                ¦Code¦
+                ¦file_path¦ src/components/common/ErrorBanner.tsx
+                ¦content¦
                 \`\`\`typescript
                 import React from 'react';
 
@@ -141,12 +141,11 @@ exports.content = `
                 ---
 
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 2
-                ¦TaskDescription¦ Modify \`ErrorBoundary.tsx\` component in \`src/components/common\` to catch
+                ¦tool_name¦ edit_file
+                ¦order_of_execution¦ 2
                 unrecoverable errors and prevent UI crashes.
-                ¦FilePath¦ src/components/common/ErrorBoundary.tsx
-                ¦FileAction¦ edit_file
-                ¦Code¦
+                ¦file_path¦ src/components/common/ErrorBoundary.tsx
+                ¦content¦
                 \`\`\`typescript
                 import React, { Component, ReactNode } from 'react';
 
@@ -159,11 +158,10 @@ exports.content = `
                 ---
 
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 3
-                ¦TaskDescription¦ Delete unused svg file.
-                ¦FilePath¦ src/asset/common/some.svg
-                ¦FileAction¦ delete_file
-                ¦Code¦
+                ¦tool_name¦ delete_file
+                ¦order_of_execution¦ 3
+                ¦file_path¦ src/asset/common/some.svg
+                ¦content¦
                 §ACTION_ITEM_END§
             </example>
 
@@ -174,11 +172,10 @@ exports.content = `
             <bad-example>
                 <why>same file multiple action</why>
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 1
-                ¦TaskDescription¦ some description
-                ¦FilePath¦ src/same-file.tsx
-                ¦FileAction¦ edit_file
-                ¦Code¦
+                ¦tool_name¦ edit_file
+                ¦order_of_execution¦ 1
+                ¦file_path¦ src/same-file.tsx
+                ¦content¦
                 \`\`\`typescript
 
                 // full content of the file
@@ -187,11 +184,10 @@ exports.content = `
                 §ACTION_ITEM_END§
 
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 2
-                ¦TaskDescription¦ some other description
-                ¦FilePath¦ src/same-file.tsx
-                ¦FileAction¦ edit_file
-                ¦Code¦
+                ¦tool_name¦ edit_file
+                ¦order_of_execution¦ 2
+                ¦file_path¦ src/same-file.tsx
+                ¦content¦
                 \`\`\`typescript
 
                 // full content of the file
@@ -204,11 +200,10 @@ exports.content = `
             <bad-example>
                 <why>one action multiple file</why>
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 1
-                ¦TaskDescription¦ some description
-                ¦FilePath¦ src/same-file.tsx, src/another-file.tsx
-                ¦FileAction¦ edit_file
-                ¦Code¦
+                ¦tool_name¦ edit_file
+                ¦order_of_execution¦ 1
+                ¦file_path¦ src/same-file.tsx, src/another-file.tsx
+                ¦content¦
                 \`\`\`typescript
 
                 // full content of the file
@@ -222,11 +217,10 @@ exports.content = `
             <bad-example>
                 <why>partial content generation</why>
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 1
-                ¦TaskDescription¦ some description
-                ¦FilePath¦ src/some-file.tsx
-                ¦FileAction¦ edit_file
-                ¦Code¦
+                ¦tool_name¦ edit_file
+                ¦order_of_execution¦ 1
+                ¦file_path¦ src/some-file.tsx
+                ¦content¦
                 \`\`\`typescript
                 import React from 'react';
                 // partial content of the file
@@ -234,17 +228,16 @@ exports.content = `
                 \`\`\`
                 §ACTION_ITEM_END§
             </bad-example>
-            
+
             you must request context before editing a file. if you never read the file content, request it first.
-            
+
             <bad-example>
                 <why>you NEVER requested this file before editing so you just destroyed the codebase</why>
                 §ACTION_ITEM_START§
-                ¦ActionNumber¦ 1
-                ¦TaskDescription¦ some stupid changes
-                ¦FilePath¦ src/some-existing-file-you-did-not-request-its-content.tsx
-                ¦FileAction¦ edit_file
-                ¦Code¦
+                ¦tool_name¦ edit_file
+                ¦order_of_execution¦ 1
+                ¦file_path¦ src/some-existing-file-you-did-not-request-its-content.tsx
+                ¦content¦
                 \`\`\`typescript
                 some stupid code changes
                 half of the content is deleted
@@ -259,23 +252,124 @@ exports.content = `
 
         </modify_file>
 
+        <quick_edit>
+            use this tool to make very small changes like fixing a typo in comments, variable names, function names,
+            class names, or other identifiers.
+            only use this tool for very small changes that do not require full file content.
+            if you need to make more than 3 changes in a file, use \`modify_file\` tool instead.
+
+            Each action item should be enclosed within \`§ACTION_ITEM_START§\` and \`§ACTION_ITEM_END§\` markers and
+            include the following details using the \`¦FieldName¦ Value\` format:
+
+            * \`¦tool_name¦\`: Always \`quick_edit\`.
+            * \`¦action¦\`: The operation to perform. Must be one of: \`insert_after\`, \`insert_before\`, \`replace\`, \`delete_block\`.
+            * \`¦search_block¦\`: A unique and exact block of code to locate the position for the edit.
+            * For \`insert_after\` and \`insert_before\`, this is the anchor. The new content will be placed relative to this block.
+            * For \`replace\` and \`delete_block\`, this is the exact content that will be replaced or removed.
+            * \`¦new_content¦\`: The new code to be added. This is required for \`insert_after\`, \`insert_before\`, and \`replace\`. It should be omitted for \`delete_block\`.
+
+
+            **RULES for \`quick_edit\`:**
+            1.  **Uniqueness is critical.** The \`¦search_block¦\` content *must* be unique within the file.
+
+            <example>
+
+                §ACTION_ITEM_START§
+                ¦tool_name¦ quick_edit
+                ¦order_of_execution¦ 1
+                ¦file_path¦ src/components/Header.tsx
+                ¦action¦ insert_after
+                ¦search_block¦
+                \`\`\`typescript
+                import React from 'react';
+                \`\`\`
+                ¦new_content¦
+                \`\`\`typescript
+                import { useTheme } from '@emotion/react';
+                \`\`\`
+                §ACTION_ITEM_END§
+
+                §ACTION_ITEM_START§
+                ¦tool_name¦ quick_edit
+                ¦order_of_execution¦ 2
+                ¦file_path¦ src/components/UserProfile.tsx
+                ¦action¦ replace
+                ¦search_block¦
+                \`\`\`jsx
+                return (
+                <div>
+                    <h1>Welcome, {name}</h1>
+                </div>
+                );
+                \`\`\`
+                ¦new_content¦
+                \`\`\`jsx
+                return (
+                <div className="profile-card">
+                    <div className="profile-info">
+                        <h2>{name}</h2>
+                        <p>Email: {email}</p>
+                    </div>
+                </div>
+                );
+                \`\`\`
+                §ACTION_ITEM_END§
+
+                §ACTION_ITEM_START§
+                ¦tool_name¦ quick_edit
+                ¦order_of_execution¦ 3
+                ¦file_path¦ src/styles/main.css
+                ¦action¦ delete_block
+                ¦search_block¦
+                \`\`\`css
+                .legacy-panel {
+                padding: 20px;
+                background-color: #eee;
+                border: 1px solid #ccc;
+                border-radius: 8px;
+                }
+                \`\`\`
+                ¦new_content¦
+                §ACTION_ITEM_END§
+            </example>
+
+            <bad-example>
+                <why>The search_block \`}\` is not unique and appears multiple times in any non-trivial TypeScript file. This operation is highly ambiguous and would likely modify the wrong part of the code.</why>
+                §ACTION_ITEM_START§
+                ¦tool_name¦ quick_edit
+                ¦order_of_execution¦ 1
+                ¦file_path¦ src/services/api.ts
+                ¦action¦ replace
+                ¦search_block¦
+                \`\`\`typescript
+                }
+                \`\`\`
+                ¦new_content¦
+                \`\`\`typescript
+                } // end of function
+                \`\`\`
+                §ACTION_ITEM_END§
+            </bad-example>
+
+        </quick_edit>
+
         <request_context>
 
             The action item should be enclosed within \`§ACTION_ITEM_START§\` and \`§ACTION_ITEM_END§\` markers and
             include the following details using the \`¦FieldName¦ Value\` format:
 
-            * \`¦FileAction¦\`: Always \`request_context\`.
-            * \`¦Files¦\`: (Optional) A comma-separated list of file paths you need to see.
-            * \`¦Folders¦\`: (Optional) A comma-separated list of folder paths you need to see.
-            * \`¦Reason¦\`: A clear and detailed explanation of why you need this context to proceed with your analysis.
+            * \`¦tool_name¦\`: Always \`request_context\`.
+            * \`¦files¦\`: (Optional) A comma-separated list of file paths you need to see.
+            * \`¦folders¦\`: (Optional) A comma-separated list of folder paths you need to see.
+            * \`¦reason¦\`: A clear and detailed explanation of why you need this context to proceed with your analysis.
             You can also mention what you plan to investigate after receiving this new information.
 
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ request_context
-                ¦Files¦ src/components/common/ErrorBoundary.tsx, src/components/common/ErrorBanner.tsx
-                ¦Reason¦ I need to understand how error handling is currently implemented in the project. By examining
+                ¦tool_name¦ request_context
+                ¦files¦ src/components/common/ErrorBoundary.tsx, src/components/common/ErrorBanner.tsx
+                ¦reason¦ I need to understand how error handling is currently implemented in the project. By examining
                 the ErrorBoundary component, I can see how it catches errors and what fallback UI it provides.
                 Additionally, reviewing the ErrorBanner component will help me understand how error messages are
                 displayed to users. This context is crucial for implementing a new feature that enhances error reporting
@@ -285,9 +379,9 @@ exports.content = `
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ request_context
-                ¦Folders¦ src/components/common
-                ¦Reason¦ I need to explore the common components used across the application to identify reusable
+                ¦tool_name¦ request_context
+                ¦folders¦ src/components/common
+                ¦reason¦ I need to explore the common components used across the application to identify reusable
                 elements and understand the overall structure. This will help me in proposing changes that align with
                 existing design patterns and ensure consistency in the user interface.
                 §ACTION_ITEM_END§
@@ -301,9 +395,9 @@ exports.content = `
                 §ACTION_ITEM_END§
 
                 §ACTION_ITEM_START§
-                ¦FileAction¦ request_context
-                ¦Folders¦ somefolder1
-                ¦Reason¦ some explanation 2
+                ¦tool_name¦ request_context
+                ¦folders¦ somefolder1
+                ¦reason¦ some explanation 2
                 §ACTION_ITEM_END§
             </bad-example>
 
@@ -318,9 +412,9 @@ exports.content = `
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ run_command
-                ¦CommandString¦ rg --files . | head -n 20
-                ¦Reason¦ I want to get a quick overview of the first 20 files in the repository to understand its
+                ¦tool_name¦ run_command
+                ¦command_string¦ rg --files . | head -n 20
+                ¦reason¦ I want to get a quick overview of the first 20 files in the repository to understand its
                 structure and identify key files that might be relevant to the user's request.
                 §ACTION_ITEM_END§
             </example>
@@ -330,33 +424,33 @@ exports.content = `
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ run_command
-                ¦CommandString¦ rg 'ErrorBoundary' .
-                ¦Reason¦ I want to locate all occurrences of the 'ErrorBoundary' component in the codebase
+                ¦tool_name¦ run_command
+                ¦command_string¦ rg 'ErrorBoundary' .
+                ¦reason¦ I want to locate all occurrences of the 'ErrorBoundary' component in the codebase
                 §ACTION_ITEM_END§
             </example>
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ run_command
-                ¦CommandString¦ ls -R src/components/common
-                ¦Reason¦ I want to list all files and directories within the \`src/components/common
+                ¦tool_name¦ run_command
+                ¦command_string¦ ls -R src/components/common
+                ¦reason¦ I want to list all files and directories within the \`src/components/common
                 §ACTION_ITEM_END§
             </example>
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ run_command
-                ¦CommandString¦ tree -L 2 src/components
-                ¦Reason¦ I want to understand the structure of the \`src/components\` directory
+                ¦tool_name¦ run_command
+                ¦command_string¦ tree -L 2 src/components
+                ¦reason¦ I want to understand the structure of the \`src/components\` directory
                 §ACTION_ITEM_END§
             </example>
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ run_command
-                ¦CommandString¦ find src/components -type d -name 'common'
-                ¦Reason¦ I want to locate the \`common\` directory within \`src/components\`
+                ¦tool_name¦ run_command
+                ¦command_string¦ find src/components -type d -name 'common'
+                ¦reason¦ I want to locate the \`common\` directory within \`src/components\`
                 §ACTION_ITEM_END§
             </example>
 
@@ -367,9 +461,9 @@ exports.content = `
                 §ACTION_ITEM_END§
 
                 §ACTION_ITEM_START§
-                ¦FileAction¦ run_command
-                ¦CommandString¦ some command 1
-                ¦Reason¦ some explanation 1
+                ¦tool_name¦ run_command
+                ¦command_string¦ some command 1
+                ¦reason¦ some explanation 1
                 §ACTION_ITEM_END§
             </bad-example>
 
@@ -382,10 +476,9 @@ exports.content = `
 
         <final>
 
-            if you use final tool, put all the content in ¦plain¦ field. do not generate anything before action item.
-            
+
             §ACTION_ITEM_START§
-            ¦FileAction¦ final
+            ¦tool_name¦ final
             ¦plain¦
             some explanation about the of the task.
             you can generate multiple lines if needed.
@@ -410,16 +503,16 @@ exports.content = `
 
             To use a tool, you must generate an action item with the following format.
 
-            * \`¦FileAction¦\`: Always \`use_mcp_tool\`.
+            * \`¦tool_name¦\`: Always \`use_mcp_tool\`.
             * \`¦server_name¦\`: The name of the MCP server providing the tool.
-            * \`¦tool_name¦\`: The name of the tool to execute.
+            * \`¦mcp_tool_name¦\`: The name of the tool to execute.
             * \`¦arguments¦\`: A JSON object containing the tool's input parameters, following the tool's input schema.
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ use_mcp_tool
+                ¦tool_name¦ use_mcp_tool
                 ¦server_name¦ linter-server
-                ¦tool_name¦ lint_file
+                ¦mcp_tool_name¦ lint_file
                 ¦arguments¦
                 {
                 "file_path": "src/some-file.ts"
@@ -429,9 +522,9 @@ exports.content = `
 
             <example>
                 §ACTION_ITEM_START§
-                ¦FileAction¦ use_mcp_tool
+                ¦tool_name¦ use_mcp_tool
                 ¦server_name¦ linter-server
-                ¦tool_name¦ get_lint_summary
+                ¦mcp_tool_name¦ get_lint_summary
                 ¦arguments¦
                 {}
                 §ACTION_ITEM_END§

package/backend/dist/src/seeding/data/system-prompts/default_master-agent.js.map

@@ -1 +1 @@
-{"version":3,"file":"default_master-agent.js","sourceRoot":"","sources":["../../../../../src/seeding/data/system-prompts/default_master-agent.ts"],"names":[],"mappings":";;;AAAa,QAAA,IAAI,GAAG,cAAc,CAAC;AACtB,QAAA,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAubtB,CAAC"}
+{"version":3,"file":"default_master-agent.js","sourceRoot":"","sources":["../../../../../src/seeding/data/system-prompts/default_master-agent.ts"],"names":[],"mappings":";;;AAAa,QAAA,IAAI,GAAG,cAAc,CAAC;AACtB,QAAA,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAohBtB,CAAC"}