repoburg 1.3.2 → 1.3.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CODEMAP.md +3 -3
- package/backend/dist/src/llm-orchestration/action-handlers/quick-edit.handler.js +2 -2
- package/backend/dist/src/llm-orchestration/action-handlers/quick-edit.handler.js.map +1 -1
- package/backend/dist/src/llm-orchestration/hooks/yolo-mode-post-execution.hook.js +6 -1
- package/backend/dist/src/llm-orchestration/hooks/yolo-mode-post-execution.hook.js.map +1 -1
- package/backend/dist/src/llm-orchestration/parser/llm-output-parser.service.js +9 -4
- package/backend/dist/src/llm-orchestration/parser/llm-output-parser.service.js.map +1 -1
- package/backend/dist/src/seeding/data/system-prompts/default_master-agent.d.ts +1 -1
- package/backend/dist/src/seeding/data/system-prompts/default_master-agent.js +15 -12
- package/backend/dist/src/seeding/data/system-prompts/default_master-agent.js.map +1 -1
- package/backend/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +1 -1
package/CODEMAP.md
CHANGED
|
@@ -78,13 +78,13 @@ The main user interface for interacting with the Repoburg backend.
|
|
|
78
78
|
### ✨ Key Directories (`frontend/src`)
|
|
79
79
|
|
|
80
80
|
- **`/app/components`**: Home to the application's React components, organized by feature:
|
|
81
|
-
- **`/pages`**: Top-level components for each main view (e.g., `MainHomePage`, `SettingsPage`).
|
|
81
|
+
- **`/pages`**: Top-level components for each main view (e.g., `MainHomePage`, `SettingsPage`). Includes the enhanced `MarkdownEditorPage`, which functions as a multi-tab code editor with features like automatic file refreshing on load, a `Cmd+P` file search palette, and advanced tab management (e.g., "close others," "close to the right" via context menu).
|
|
82
82
|
- **`/editors`**: Specialized editor components for templates, prompts, and snippets.
|
|
83
83
|
- **`/plan` & `/session`**: Components for displaying AI-generated plans and the conversation history. `ActionItemContent.tsx` is the key component for rendering individual AI actions, including the new `quick_edit` (as a diff) and `final` (as formatted markdown) action types.
|
|
84
|
-
- **`/common`**: Shared components like the command palette, markdown renderers, and the new `VariableToggleModal`.
|
|
84
|
+
- **`/common`**: Shared components like the command palette, markdown renderers, and the new `VariableToggleModal`. This directory also includes the `GlobalFileSearchPalette`, which provides a `Cmd+P` interface for quick file searching and opening.
|
|
85
85
|
- **`/components/ui`**: The library of low-level, reusable UI components from shadcn/ui.
|
|
86
86
|
- **`/lib/api`**: A collection of strongly-typed functions that handle all HTTP communication with the `backend` API, including the new `customVariable` client.
|
|
87
|
-
- **`/store`**: Contains all Zustand state management logic, divided into slices for different features (e.g., `session.slice.ts`, `ui.slice.ts`, `customVariableStore.ts`).
|
|
87
|
+
- **`/store`**: Contains all Zustand state management logic, divided into slices for different features (e.g., `session.slice.ts`, `ui.slice.ts`, `customVariableStore.ts`, `markdownEditorStore.ts`).
|
|
88
88
|
- **`/hooks`**: Custom React hooks, such as `useMonacoEtaSetup`, which now provides autocompletion for Repoburg Variables (`it.VAR`).
|
|
89
89
|
- **`/types`**: Contains all TypeScript type definitions for API payloads and other shared data structures.
|
|
90
90
|
|
|
@@ -102,10 +102,10 @@ let QuickEditHandler = QuickEditHandler_1 = class QuickEditHandler {
|
|
|
102
102
|
newFileContent = `${before}${new_content}${after}`;
|
|
103
103
|
break;
|
|
104
104
|
case 'insert_after':
|
|
105
|
-
newFileContent = `${before}${search_block}${new_content}${after}`;
|
|
105
|
+
newFileContent = `${before}${search_block}\n${new_content}${after}`;
|
|
106
106
|
break;
|
|
107
107
|
case 'insert_before':
|
|
108
|
-
newFileContent = `${before}${new_content}${search_block}${after}`;
|
|
108
|
+
newFileContent = `${before}${new_content}\n${search_block}${after}`;
|
|
109
109
|
break;
|
|
110
110
|
case 'delete_block':
|
|
111
111
|
newFileContent = `${before}${after}`;
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"quick-edit.handler.js","sourceRoot":"","sources":["../../../../src/llm-orchestration/action-handlers/quick-edit.handler.ts"],"names":[],"mappings":";;;;;;;;;;AAAA,2CAKwB;AACxB,kCAAkC;AAClC,6BAA6B;AAC7B,yDAAiD;AACjD,qDAA2C;AAM3C,iFAA4E;AAC5E,mEAA6D;AAGtD,IAAM,gBAAgB,wBAAtB,MAAM,gBAAgB;IAAtB;QACI,aAAQ,GAAG,YAAY,CAAC;QAChB,WAAM,GAAG,IAAI,eAAM,CAAC,kBAAgB,CAAC,IAAI,CAAC,CAAC;QAC3C,gBAAW,GAC1B,OAAO,CAAC,GAAG,CAAC,qBAAqB,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC;IAsIvD,CAAC;IApIS,sBAAsB,CAAC,UAAkB;QAC/C,MAAM,cAAc,GAAG,IAAI,CAAC,SAAS,CAAC,UAAU,CAAC,CAAC;QAClD,IAAI,IAAI,CAAC,UAAU,CAAC,cAAc,CAAC,EAAE,CAAC;YACpC,MAAM,IAAI,4BAAmB,CAC3B,mCAAmC,UAAU,EAAE,CAChD,CAAC;QACJ,CAAC;QACD,MAAM,YAAY,GAAG,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,WAAW,EAAE,cAAc,CAAC,CAAC;QACpE,IAAI,CAAC,YAAY,CAAC,UAAU,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE,CAAC;YAC/C,MAAM,IAAI,4BAAmB,CAC3B,kCAAkC,UAAU,EAAE,CAC/C,CAAC;QACJ,CAAC;QACD,OAAO,YAAY,CAAC;IACtB,CAAC;IAEO,WAAW,CACjB,QAAgB,EAChB,MAAqD,EACrD,WAAmB;QAEnB,IAAI,UAAkB,CAAC;QACvB,QAAQ,MAAM,EAAE,CAAC;YACf,KAAK,WAAW;gBACd,UAAU,GAAG,sCAAsC,CAAC;gBACpD,MAAM;YACR,KAAK,YAAY;gBACf,UAAU;oBACR,oEAAoE,CAAC;gBACvE,MAAM;YACR,KAAK,gBAAgB;gBACnB,UAAU,GAAG,wCAAwC,CAAC;gBACtD,MAAM;QACV,CAAC;QACD,OAAO,aAAa,QAAQ,kCAAkC,UAAU,gDAAgD,WAAW,8FAA8F,CAAC;IACpO,CAAC;IAED,KAAK,CAAC,OAAO,CACX,IAA4B,EAC5B,OAA6B;QAE7B,MAAM,aAAa,GAAG,IAAA,gCAAY,EAAC,sCAAgB,EAAE,IAAI,CAAC,CAAC;QAC3D,MAAM,MAAM,GAAG,MAAM,IAAA,0BAAQ,EAAC,aAAa,CAAC,CAAC;QAC7C,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACtB,MAAM,aAAa,GAAG,MAAM;iBACzB,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,GAAG,CAAC,WAAW,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;iBAC7D,IAAI,CAAC,IAAI,CAAC,CAAC;YACd,MAAM,IAAI,iDAAsB,CAAC,aAAa,CAAC,CAAC;QAClD,CAAC;QAED,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,YAAY,EAAE,WAAW,EAAE,GAAG,aAAa,CAAC;QACvE,MAAM,QAAQ,GAAG,IAAI,CAAC,sBAAsB,CAAC,SAAS,CAAC,CAAC;QAExD,MAAM,eAAe,GAAG,MAAM,EAAE;aAC7B,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;aAC1B,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;YACf,IAAI,KAAK,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;gBAC5B,OAAO,IAAI,CAAC;YACd,CAAC;YACD,MAAM,KAAK,CAAC;QACd,CAAC,CAAC,CAAC;QAEL,IAAI,eAAe,KAAK,IAAI,EAAE,CAAC;YAC7B,MAAM,YAAY,GAAG,IAAI,CAAC,WAAW,CACnC,SAAS,EACT,gBAAgB,EAChB,YAAY,CACb,CAAC;YACF,OAAO,CAAC,QAAQ,CAAC,gBAAgB,CAAC,IAAI,CAAC;gBACrC,SAAS,EAAE,IAAI,CAAC,QAAQ;gBACxB,KAAK,EAAE,YAAY;aACpB,CAAC,CAAC;YACH,OAAO;gBACL,MAAM,EAAE,SAAS;gBACjB,OAAO,EAAE,kBAAkB,SAAS,2BAA2B;gBAC/D,aAAa,EAAE,YAAY;gBAC3B,cAAc,EAAE,aAAa;aAC9B,CAAC;QACJ,CAAC;QAED,MAAM,KAAK,GAAG,eAAe,CAAC,KAAK,CAAC,YAAY,CAAC,CAAC;QAElD,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YACvB,MAAM,MAAM,GAAG,KAAK,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,YAAY,CAAC;YAC/D,MAAM,YAAY,GAAG,IAAI,CAAC,WAAW,CAAC,SAAS,EAAE,MAAM,EAAE,YAAY,CAAC,CAAC;YACvE,OAAO,CAAC,QAAQ,CAAC,gBAAgB,CAAC,IAAI,CAAC;gBACrC,SAAS,EAAE,IAAI,CAAC,QAAQ;gBACxB,KAAK,EAAE,YAAY;aACpB,CAAC,CAAC;YACH,OAAO;gBACL,MAAM,EAAE,SAAS;gBACjB,OAAO,EAAE,kBAAkB,SAAS,iCAAiC,MAAM,IAAI;gBAC/E,aAAa,EAAE,YAAY;gBAC3B,cAAc,EAAE,aAAa;aAC9B,CAAC;QACJ,CAAC;QAED,IAAI,cAAsB,CAAC;QAC3B,MAAM,CAAC,MAAM,EAAE,KAAK,CAAC,GAAG,KAAK,CAAC;QAE9B,QAAQ,MAAM,EAAE,CAAC;YACf,KAAK,SAAS;gBACZ,cAAc,GAAG,GAAG,MAAM,GAAG,WAAW,GAAG,KAAK,EAAE,CAAC;gBACnD,MAAM;YACR,KAAK,cAAc;gBACjB,cAAc,GAAG,GAAG,MAAM,GAAG,YAAY,
|
|
1
|
+
{"version":3,"file":"quick-edit.handler.js","sourceRoot":"","sources":["../../../../src/llm-orchestration/action-handlers/quick-edit.handler.ts"],"names":[],"mappings":";;;;;;;;;;AAAA,2CAKwB;AACxB,kCAAkC;AAClC,6BAA6B;AAC7B,yDAAiD;AACjD,qDAA2C;AAM3C,iFAA4E;AAC5E,mEAA6D;AAGtD,IAAM,gBAAgB,wBAAtB,MAAM,gBAAgB;IAAtB;QACI,aAAQ,GAAG,YAAY,CAAC;QAChB,WAAM,GAAG,IAAI,eAAM,CAAC,kBAAgB,CAAC,IAAI,CAAC,CAAC;QAC3C,gBAAW,GAC1B,OAAO,CAAC,GAAG,CAAC,qBAAqB,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC;IAsIvD,CAAC;IApIS,sBAAsB,CAAC,UAAkB;QAC/C,MAAM,cAAc,GAAG,IAAI,CAAC,SAAS,CAAC,UAAU,CAAC,CAAC;QAClD,IAAI,IAAI,CAAC,UAAU,CAAC,cAAc,CAAC,EAAE,CAAC;YACpC,MAAM,IAAI,4BAAmB,CAC3B,mCAAmC,UAAU,EAAE,CAChD,CAAC;QACJ,CAAC;QACD,MAAM,YAAY,GAAG,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,WAAW,EAAE,cAAc,CAAC,CAAC;QACpE,IAAI,CAAC,YAAY,CAAC,UAAU,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE,CAAC;YAC/C,MAAM,IAAI,4BAAmB,CAC3B,kCAAkC,UAAU,EAAE,CAC/C,CAAC;QACJ,CAAC;QACD,OAAO,YAAY,CAAC;IACtB,CAAC;IAEO,WAAW,CACjB,QAAgB,EAChB,MAAqD,EACrD,WAAmB;QAEnB,IAAI,UAAkB,CAAC;QACvB,QAAQ,MAAM,EAAE,CAAC;YACf,KAAK,WAAW;gBACd,UAAU,GAAG,sCAAsC,CAAC;gBACpD,MAAM;YACR,KAAK,YAAY;gBACf,UAAU;oBACR,oEAAoE,CAAC;gBACvE,MAAM;YACR,KAAK,gBAAgB;gBACnB,UAAU,GAAG,wCAAwC,CAAC;gBACtD,MAAM;QACV,CAAC;QACD,OAAO,aAAa,QAAQ,kCAAkC,UAAU,gDAAgD,WAAW,8FAA8F,CAAC;IACpO,CAAC;IAED,KAAK,CAAC,OAAO,CACX,IAA4B,EAC5B,OAA6B;QAE7B,MAAM,aAAa,GAAG,IAAA,gCAAY,EAAC,sCAAgB,EAAE,IAAI,CAAC,CAAC;QAC3D,MAAM,MAAM,GAAG,MAAM,IAAA,0BAAQ,EAAC,aAAa,CAAC,CAAC;QAC7C,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACtB,MAAM,aAAa,GAAG,MAAM;iBACzB,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,GAAG,CAAC,WAAW,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;iBAC7D,IAAI,CAAC,IAAI,CAAC,CAAC;YACd,MAAM,IAAI,iDAAsB,CAAC,aAAa,CAAC,CAAC;QAClD,CAAC;QAED,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,YAAY,EAAE,WAAW,EAAE,GAAG,aAAa,CAAC;QACvE,MAAM,QAAQ,GAAG,IAAI,CAAC,sBAAsB,CAAC,SAAS,CAAC,CAAC;QAExD,MAAM,eAAe,GAAG,MAAM,EAAE;aAC7B,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;aAC1B,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;YACf,IAAI,KAAK,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;gBAC5B,OAAO,IAAI,CAAC;YACd,CAAC;YACD,MAAM,KAAK,CAAC;QACd,CAAC,CAAC,CAAC;QAEL,IAAI,eAAe,KAAK,IAAI,EAAE,CAAC;YAC7B,MAAM,YAAY,GAAG,IAAI,CAAC,WAAW,CACnC,SAAS,EACT,gBAAgB,EAChB,YAAY,CACb,CAAC;YACF,OAAO,CAAC,QAAQ,CAAC,gBAAgB,CAAC,IAAI,CAAC;gBACrC,SAAS,EAAE,IAAI,CAAC,QAAQ;gBACxB,KAAK,EAAE,YAAY;aACpB,CAAC,CAAC;YACH,OAAO;gBACL,MAAM,EAAE,SAAS;gBACjB,OAAO,EAAE,kBAAkB,SAAS,2BAA2B;gBAC/D,aAAa,EAAE,YAAY;gBAC3B,cAAc,EAAE,aAAa;aAC9B,CAAC;QACJ,CAAC;QAED,MAAM,KAAK,GAAG,eAAe,CAAC,KAAK,CAAC,YAAY,CAAC,CAAC;QAElD,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YACvB,MAAM,MAAM,GAAG,KAAK,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,YAAY,CAAC;YAC/D,MAAM,YAAY,GAAG,IAAI,CAAC,WAAW,CAAC,SAAS,EAAE,MAAM,EAAE,YAAY,CAAC,CAAC;YACvE,OAAO,CAAC,QAAQ,CAAC,gBAAgB,CAAC,IAAI,CAAC;gBACrC,SAAS,EAAE,IAAI,CAAC,QAAQ;gBACxB,KAAK,EAAE,YAAY;aACpB,CAAC,CAAC;YACH,OAAO;gBACL,MAAM,EAAE,SAAS;gBACjB,OAAO,EAAE,kBAAkB,SAAS,iCAAiC,MAAM,IAAI;gBAC/E,aAAa,EAAE,YAAY;gBAC3B,cAAc,EAAE,aAAa;aAC9B,CAAC;QACJ,CAAC;QAED,IAAI,cAAsB,CAAC;QAC3B,MAAM,CAAC,MAAM,EAAE,KAAK,CAAC,GAAG,KAAK,CAAC;QAE9B,QAAQ,MAAM,EAAE,CAAC;YACf,KAAK,SAAS;gBACZ,cAAc,GAAG,GAAG,MAAM,GAAG,WAAW,GAAG,KAAK,EAAE,CAAC;gBACnD,MAAM;YACR,KAAK,cAAc;gBACjB,cAAc,GAAG,GAAG,MAAM,GAAG,YAAY,KAAK,WAAW,GAAG,KAAK,EAAE,CAAC;gBACpE,MAAM;YACR,KAAK,eAAe;gBAClB,cAAc,GAAG,GAAG,MAAM,GAAG,WAAW,KAAK,YAAY,GAAG,KAAK,EAAE,CAAC;gBACpE,MAAM;YACR,KAAK,cAAc;gBACjB,cAAc,GAAG,GAAG,MAAM,GAAG,KAAK,EAAE,CAAC;gBACrC,MAAM;QACV,CAAC;QAED,IAAI,CAAC;YACH,MAAM,EAAE,CAAC,SAAS,CAAC,QAAQ,EAAE,cAAc,EAAE,MAAM,CAAC,CAAC;YACrD,OAAO;gBACL,MAAM,EAAE,SAAS;gBACjB,OAAO,EAAE,SAAS,SAAS,0CAA0C;gBACrE,cAAc,EAAE,EAAE,GAAG,aAAa,EAAE,OAAO,EAAE,cAAc,EAAE;gBAC7D,2BAA2B,EAAE,eAAe;aAC7C,CAAC;QACJ,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,IAAI,CAAC,MAAM,CAAC,KAAK,CACf,0CAA0C,SAAS,KAAK,KAAK,CAAC,OAAO,EAAE,CACxE,CAAC;YACF,MAAM,IAAI,qCAA4B,CACpC,8BAA8B,SAAS,MAAM,KAAK,CAAC,OAAO,EAAE,CAC7D,CAAC;QACJ,CAAC;IACH,CAAC;CACF,CAAA;AA1IY,4CAAgB;2BAAhB,gBAAgB;IAD5B,IAAA,mBAAU,GAAE;GACA,gBAAgB,CA0I5B"}
|
|
@@ -17,7 +17,12 @@ exports.YoloModePostExecutionHook = void 0;
|
|
|
17
17
|
const common_1 = require("@nestjs/common");
|
|
18
18
|
const application_state_service_1 = require("../../application-state/application-state.service");
|
|
19
19
|
const chat_service_1 = require("../../interactive-chat/chat.service");
|
|
20
|
-
const FILE_MODIFICATION_ACTIONS = [
|
|
20
|
+
const FILE_MODIFICATION_ACTIONS = [
|
|
21
|
+
'create_file',
|
|
22
|
+
'edit_file',
|
|
23
|
+
'delete_file',
|
|
24
|
+
'quick_edit',
|
|
25
|
+
];
|
|
21
26
|
let YoloModePostExecutionHook = YoloModePostExecutionHook_1 = class YoloModePostExecutionHook {
|
|
22
27
|
constructor(appStateService, chatService) {
|
|
23
28
|
this.appStateService = appStateService;
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"yolo-mode-post-execution.hook.js","sourceRoot":"","sources":["../../../../src/llm-orchestration/hooks/yolo-mode-post-execution.hook.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;AAAA,2CAAwE;AAIxE,iGAA4F;AAC5F,sEAAkE;AAElE,MAAM,yBAAyB,GAAG,
|
|
1
|
+
{"version":3,"file":"yolo-mode-post-execution.hook.js","sourceRoot":"","sources":["../../../../src/llm-orchestration/hooks/yolo-mode-post-execution.hook.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;AAAA,2CAAwE;AAIxE,iGAA4F;AAC5F,sEAAkE;AAElE,MAAM,yBAAyB,GAAG;IAChC,aAAa;IACb,WAAW;IACX,aAAa;IACb,YAAY;CACb,CAAC;AAGK,IAAM,yBAAyB,iCAA/B,MAAM,yBAAyB;IAGpC,YACmB,eAAwC,EAEzD,WAAyC;QAFxB,oBAAe,GAAf,eAAe,CAAyB;QAExC,gBAAW,GAAX,WAAW,CAAa;QAL1B,WAAM,GAAG,IAAI,eAAM,CAAC,2BAAyB,CAAC,IAAI,CAAC,CAAC;IAMlE,CAAC;IAEJ,KAAK,CAAC,GAAG,CACP,YAA0B,EAC1B,OAA6B;QAE7B,MAAM,UAAU,GAAG,MAAM,IAAI,CAAC,eAAe,CAAC,kBAAkB,EAAE,CAAC;QACnE,IAAI,CAAC,UAAU,EAAE,CAAC;YAChB,OAAO;QACT,CAAC;QAED,MAAM,cAAc,GAAG,OAAO,CAAC,qBAAqB,CAAC,IAAI,CACvD,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,SAAS,KAAK,OAAO,CAC/B,CAAC;QACF,IAAI,cAAc,EAAE,CAAC;YACnB,IAAI,CAAC,MAAM,CAAC,GAAG,CACb,0DAA0D,CAC3D,CAAC;YACF,MAAM,IAAI,CAAC,eAAe,CAAC,kBAAkB,CAAC,KAAK,CAAC,CAAC;YACrD,OAAO;QACT,CAAC;QAED,MAAM,mBAAmB,GAAG,OAAO,CAAC,qBAAqB,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CACnE,yBAAyB,CAAC,QAAQ,CAAC,CAAC,CAAC,SAAS,CAAC,CAChD,CAAC;QAEF,IAAI,mBAAmB,EAAE,CAAC;YACxB,IAAI,CAAC,MAAM,CAAC,GAAG,CACb,kEAAkE,CACnE,CAAC;YACF,MAAM,YAAY,GAAG,MAAM,IAAI,CAAC,eAAe,CAAC,mBAAmB,EAAE,CAAC;YAEtE,IAAI,CAAC,WAAW;iBACb,WAAW,CAAC,YAAY,CAAC,UAAU,EAAE,MAAM,EAAE,YAAY,CAAC;iBAC1D,KAAK,CAAC,CAAC,GAAG,EAAE,EAAE,CACb,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,0BAA0B,GAAG,CAAC,OAAO,EAAE,CAAC,CAC3D,CAAC;QACN,CAAC;IACH,CAAC;CACF,CAAA;AA9CY,8DAAyB;oCAAzB,yBAAyB;IADrC,IAAA,mBAAU,GAAE;IAMR,WAAA,IAAA,eAAM,EAAC,IAAA,mBAAU,EAAC,GAAG,EAAE,CAAC,0BAAW,CAAC,CAAC,CAAA;qCADJ,mDAAuB;QAE3B,0BAAW;GANhC,yBAAyB,CA8CrC"}
|
|
@@ -18,7 +18,11 @@ let LlmOutputParserService = LlmOutputParserService_1 = class LlmOutputParserSer
|
|
|
18
18
|
if (!rawResponse || rawResponse.trim() === '') {
|
|
19
19
|
return { explanation: null, actions: [] };
|
|
20
20
|
}
|
|
21
|
-
const
|
|
21
|
+
const startTagRegex = new RegExp(parsing_constants_1.ACTION_ITEM_START_TAG, 'i');
|
|
22
|
+
const firstActionStartMatch = rawResponse.match(startTagRegex);
|
|
23
|
+
const firstActionStart = firstActionStartMatch
|
|
24
|
+
? firstActionStartMatch.index
|
|
25
|
+
: -1;
|
|
22
26
|
let explanation = null;
|
|
23
27
|
let actionsPart = rawResponse;
|
|
24
28
|
if (firstActionStart > 0) {
|
|
@@ -26,12 +30,13 @@ let LlmOutputParserService = LlmOutputParserService_1 = class LlmOutputParserSer
|
|
|
26
30
|
actionsPart = rawResponse.substring(firstActionStart);
|
|
27
31
|
}
|
|
28
32
|
else if (firstActionStart === -1) {
|
|
29
|
-
|
|
33
|
+
const partialEndTagRegex = new RegExp(parsing_constants_1.PARTIAL_ACTION_ITEM_END_TAG, 'i');
|
|
34
|
+
if (!partialEndTagRegex.test(rawResponse)) {
|
|
30
35
|
return { explanation: rawResponse.trim(), actions: [] };
|
|
31
36
|
}
|
|
32
37
|
}
|
|
33
38
|
const actionBlocks = actionsPart
|
|
34
|
-
.split(
|
|
39
|
+
.split(startTagRegex)
|
|
35
40
|
.filter((block) => block.trim() !== '');
|
|
36
41
|
if (actionBlocks.length === 0) {
|
|
37
42
|
this.logger.log('No action item blocks found in the response.');
|
|
@@ -40,7 +45,7 @@ let LlmOutputParserService = LlmOutputParserService_1 = class LlmOutputParserSer
|
|
|
40
45
|
const parsedActions = [];
|
|
41
46
|
for (const block of actionBlocks) {
|
|
42
47
|
try {
|
|
43
|
-
const endTagRegex = new RegExp(`${parsing_constants_1.PARTIAL_ACTION_ITEM_END_TAG}${parsing_constants_1.SPECIAL_ACTION_ITEM_TOKEN}
|
|
48
|
+
const endTagRegex = new RegExp(`${parsing_constants_1.PARTIAL_ACTION_ITEM_END_TAG}${parsing_constants_1.SPECIAL_ACTION_ITEM_TOKEN}?`, 'i');
|
|
44
49
|
const cleanBlock = block.split(endTagRegex)[0].trim();
|
|
45
50
|
const actionArgs = {};
|
|
46
51
|
const fieldRegex = new RegExp(`${parsing_constants_1.SPECIAL_FIELD_TOKEN}(.*?)${parsing_constants_1.SPECIAL_FIELD_TOKEN}`, 'g');
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"llm-output-parser.service.js","sourceRoot":"","sources":["../../../../src/llm-orchestration/parser/llm-output-parser.service.ts"],"names":[],"mappings":";;;;;;;;;;AAAA,2CAAoD;AAEpD,2DAO6B;AAGtB,IAAM,sBAAsB,8BAA5B,MAAM,sBAAsB;IAA5B;QACY,WAAM,GAAG,IAAI,eAAM,CAAC,wBAAsB,CAAC,IAAI,CAAC,CAAC;
|
|
1
|
+
{"version":3,"file":"llm-output-parser.service.js","sourceRoot":"","sources":["../../../../src/llm-orchestration/parser/llm-output-parser.service.ts"],"names":[],"mappings":";;;;;;;;;;AAAA,2CAAoD;AAEpD,2DAO6B;AAGtB,IAAM,sBAAsB,8BAA5B,MAAM,sBAAsB;IAA5B;QACY,WAAM,GAAG,IAAI,eAAM,CAAC,wBAAsB,CAAC,IAAI,CAAC,CAAC;IA6IpE,CAAC;IArIC,KAAK,CAAC,KAAK,CAAC,WAAmB;QAC7B,IAAI,CAAC,WAAW,IAAI,WAAW,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC;YAC9C,OAAO,EAAE,WAAW,EAAE,IAAI,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC;QAC5C,CAAC;QAED,MAAM,aAAa,GAAG,IAAI,MAAM,CAAC,yCAAqB,EAAE,GAAG,CAAC,CAAC;QAC7D,MAAM,qBAAqB,GAAG,WAAW,CAAC,KAAK,CAAC,aAAa,CAAC,CAAC;QAC/D,MAAM,gBAAgB,GAAG,qBAAqB;YAC5C,CAAC,CAAC,qBAAqB,CAAC,KAAK;YAC7B,CAAC,CAAC,CAAC,CAAC,CAAC;QAEP,IAAI,WAAW,GAAkB,IAAI,CAAC;QACtC,IAAI,WAAW,GAAG,WAAW,CAAC;QAE9B,IAAI,gBAAgB,GAAG,CAAC,EAAE,CAAC;YACzB,WAAW,GAAG,WAAW,CAAC,SAAS,CAAC,CAAC,EAAE,gBAAgB,CAAC,CAAC,IAAI,EAAE,CAAC;YAChE,WAAW,GAAG,WAAW,CAAC,SAAS,CAAC,gBAAgB,CAAC,CAAC;QACxD,CAAC;aAAM,IAAI,gBAAgB,KAAK,CAAC,CAAC,EAAE,CAAC;YAGnC,MAAM,kBAAkB,GAAG,IAAI,MAAM,CAAC,+CAA2B,EAAE,GAAG,CAAC,CAAC;YACxE,IAAI,CAAC,kBAAkB,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE,CAAC;gBAC1C,OAAO,EAAE,WAAW,EAAE,WAAW,CAAC,IAAI,EAAE,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC;YAC1D,CAAC;QACH,CAAC;QAED,MAAM,YAAY,GAAG,WAAW;aAC7B,KAAK,CAAC,aAAa,CAAC;aACpB,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC;QAE1C,IAAI,YAAY,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAC9B,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,8CAA8C,CAAC,CAAC;YAChE,OAAO,EAAE,WAAW,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC;QACtC,CAAC;QAED,MAAM,aAAa,GAAa,EAAE,CAAC;QACnC,KAAK,MAAM,KAAK,IAAI,YAAY,EAAE,CAAC;YACjC,IAAI,CAAC;gBACH,MAAM,WAAW,GAAG,IAAI,MAAM,CAC5B,GAAG,+CAA2B,GAAG,6CAAyB,GAAG,EAC7D,GAAG,CACJ,CAAC;gBACF,MAAM,UAAU,GAAG,KAAK,CAAC,KAAK,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;gBAEtD,MAAM,UAAU,GAA2B,EAAE,CAAC;gBAC9C,MAAM,UAAU,GAAG,IAAI,MAAM,CAC3B,GAAG,uCAAmB,QAAQ,uCAAmB,EAAE,EACnD,GAAG,CACJ,CAAC;gBACF,MAAM,OAAO,GAAG,EAAE,CAAC;gBACnB,IAAI,KAAK,CAAC;gBAGV,OAAO,CAAC,KAAK,GAAG,UAAU,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC,KAAK,IAAI,EAAE,CAAC;oBACtD,OAAO,CAAC,IAAI,CAAC;wBACX,GAAG,EAAE,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE;wBACpB,KAAK,EAAE,KAAK,CAAC,KAAK;wBAClB,YAAY,EAAE,KAAK,CAAC,CAAC,CAAC,CAAC,MAAM;qBAC9B,CAAC,CAAC;gBACL,CAAC;gBAED,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;oBACzB,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,uCAAuC,CAAC,CAAC;oBAC1D,SAAS;gBACX,CAAC;gBAGD,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;oBACxC,MAAM,YAAY,GAAG,OAAO,CAAC,CAAC,CAAC,CAAC;oBAChC,MAAM,SAAS,GAAG,OAAO,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC;oBACjC,MAAM,eAAe,GACnB,YAAY,CAAC,KAAK,GAAG,YAAY,CAAC,YAAY,CAAC;oBACjD,MAAM,aAAa,GAAG,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,KAAK,CAAC,CAAC,CAAC,UAAU,CAAC,MAAM,CAAC;oBACtE,MAAM,KAAK,GAAG,UAAU;yBACrB,SAAS,CAAC,eAAe,EAAE,aAAa,CAAC;yBACzC,IAAI,EAAE,CAAC;oBAEV,MAAM,GAAG,GAAG,YAAY,CAAC,GAAG;yBACzB,WAAW,EAAE;yBACb,OAAO,CAAC,cAAc,EAAE,EAAE,CAAC,CAAC;oBAE/B,IAAI,CAAC,GAAG,EAAE,CAAC;wBACT,IAAI,CAAC,MAAM,CAAC,IAAI,CACd,uEAAuE,YAAY,CAAC,GAAG,GAAG,CAC3F,CAAC;wBACF,SAAS;oBACX,CAAC;oBAID,IAAI,CAAC,CAAC,GAAG,IAAI,UAAU,CAAC,EAAE,CAAC;wBACzB,UAAU,CAAC,GAAG,CAAC,GAAG,KAAK,CAAC;oBAC1B,CAAC;gBACH,CAAC;gBAED,MAAM,WAAW,GAAG,mCAAe,CAAC,WAAW,EAAE,CAAC;gBAClD,MAAM,QAAQ,GAAG,UAAU,CAAC,WAAW,CAAC,CAAC;gBAEzC,IAAI,CAAC,QAAQ,IAAI,OAAO,QAAQ,KAAK,QAAQ,EAAE,CAAC;oBAC9C,IAAI,CAAC,MAAM,CAAC,IAAI,CACd,8DAA8D,CAC/D,CAAC;oBACF,SAAS;gBACX,CAAC;gBAGD,OAAO,UAAU,CAAC,WAAW,CAAC,CAAC;gBAE/B,MAAM,SAAS,GAAW;oBACxB,SAAS,EAAE,QAAQ;oBACnB,SAAS,EAAE,UAAU;iBACtB,CAAC;gBACF,aAAa,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;YAChC,CAAC;YAAC,OAAO,KAAK,EAAE,CAAC;gBACf,IAAI,CAAC,MAAM,CAAC,IAAI,CACd,iDAAiD,KAAK,CAAC,OAAO,EAAE,EAChE,kBAAkB,KAAK,CAAC,SAAS,CAAC,CAAC,EAAE,GAAG,CAAC,KAAK,CAC/C,CAAC;YACJ,CAAC;QACH,CAAC;QAGD,aAAa,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE;YAC1B,MAAM,MAAM,GAAG,CAAC,CAAC,SAAS,CAAC,4CAAwB,CAAC,CAAC;YACrD,MAAM,MAAM,GAAG,CAAC,CAAC,SAAS,CAAC,4CAAwB,CAAC,CAAC;YACrD,IAAI,MAAM,KAAK,SAAS,IAAI,MAAM,KAAK,SAAS;gBAAE,OAAO,CAAC,CAAC;YAC3D,IAAI,MAAM,KAAK,SAAS;gBAAE,OAAO,CAAC,CAAC;YACnC,IAAI,MAAM,KAAK,SAAS;gBAAE,OAAO,CAAC,CAAC,CAAC;YACpC,OAAO,QAAQ,CAAC,MAAM,EAAE,EAAE,CAAC,GAAG,QAAQ,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC;QACrD,CAAC,CAAC,CAAC;QAEH,OAAO,EAAE,WAAW,EAAE,OAAO,EAAE,aAAa,EAAE,CAAC;IACjD,CAAC;CACF,CAAA;AA9IY,wDAAsB;iCAAtB,sBAAsB;IADlC,IAAA,mBAAU,GAAE;GACA,sBAAsB,CA8IlC"}
|
|
@@ -1,2 +1,2 @@
|
|
|
1
1
|
export declare const name = "Master Agent";
|
|
2
|
-
export declare const content = "\n<ai>\n <definition>you are a software developer AI agent. you're talking to a software developer. your task is implementing\n new feature, fixing bugs, explaining codebase or just helping to the user\n </definition>\n\n <preparation-phase-loop>\n\n <clear-the-request>\n user provides a request for code or software development task. and they might provide relevant context (code\n files, file/folder tree structure, docs or code snippets).\n first make sure you understand the request. if you don't understand, ask for clarification.\n </clear-the-request>\n\n <build-context>\n you're always working within a code repository. meticulously search codebase to find where to work and find\n relevant examples or documentations.\n you have 3 tools:\n 1- `request_context`: with this tool you can ask files and folders. you will get the content of files in\n response. if you ask folder you will get all the files content in that folder and its subfolders.\n 2- `run_command`: with this tool you can run any command line commands. for example rg, tree, ls, find\n etc. note: use tree over ls\n 3- `use_mcp_tool`: if there is any mcp server connected, you can use its tools to get more context. if\n it's not possible with native tools.\n\n this step is a loop. you should use this step as exploration phase.\n never stop exploring until you are 100% sure you have all the context you need to work on the request.\n you are encouraged to ask more context to validate your assumptions.\n </build-context>\n\n <propose-changes>\n if you reach this phase you are 100% sure you have all the context you need to work on the request.\n now you should propose the changes you will make to fulfill the request.\n be concise in your proposal. explain with code snippets if needed.\n\n if you propose a change on something make sure you requested its context before.\n\n use `final` tool to explain your proposal.\n </propose-changes>\n\n\n <desicion-point>\n if user agrees with your proposal, you can move to implementation phase.\n if user disagrees or wants changes, go back to `clear-the-request` phase.\n\n </desicion-point>\n\n </preparation-phase-loop>\n\n <implementation-phase>\n you will modify the codebase to fulfill the request. you can create, update or delete files.\n you have 2 tools:\n 1- `modify_file`: with this tool you can create, edit or delete files.\n 2- `quick_edit`: with this tool you can make small changes on exiting files.\n\n\n - rule: NEVER EDIT (`modify_file` or `quick_edit` command) A FILE BEFORE REQUESTING CONTEXT. if you don't have the file content,\n request it first (`request_context` command).\n\n - scope: only code what you propose and user agrees. do not refactor code or change anything that is not related\n to the request.\n - file size: keep files are small as possible. if a file is getting too big, split it into smaller files.\n - commenting: only use comments when you absolutely need to explain something. otherwise write self-explanatory\n code.\n\n </implementation-phase>\n\n\n <user-feedbck>\n if user is not satisfied with your implementation, go back to `clear-the-request` phase.\n if user says `yolo` in response, you can continue. if you're done, explain what you did with `final` tool.\n </user-feedbck>\n\n\n <using-mcp-tools>\n if there is any mcp server available, you can use its tools to get more context or do some tasks.\n use `use_mcp_tool` tool to use mcp server tools.\n make sure to follow the instructions for `use_mcp_tool` tool below.\n RULE: always prioritize native tools over mcp tools.\n </using-mcp-tools>\n\n <tools>\n\n you have 4 tools: `modify_file`, `quick_edit`, `request_context` and `run_command`. you also have `final` tool to\n explain your proposal or explain the task you did.\n make sure to use only one tool per action item. never combine multiple tools in a single action item or never\n generate multiple action items for same tool.\n make sure to follow the instructions for each tool below.\n\n <modify_file>\n\n Based on the user request, you must generate a numbered list of action items.\n Each action item represents the *complete* set of modifications for a *single* file.\n Action items are ordered sequentially.\n Each action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n\n \u00A7TITLE_START\u00A7 very brief title for entire chat history including previous prompt, if current title is fine\n then leave it (max 4 words) \u00A7TITLE_END\u00A7\n\n * `\u00A6tool_name\u00A6`: The operation to perform: `create_file`, `edit_file`, `delete_file`\n * `\u00A6order_of_execution\u00A6`: The sequential identifier for the task.\n * `\u00A6file_path\u00A6`: The file path where the modification will occur (ensure it aligns with the *Project Files\n from Structure*).\n * `\u00A6content\u00A6`:\n * For `create_file`: Provide the complete content of the new file within a code block.\n * For `edit_file`: Provide the complete content with modifications of the new file within a code block.\n * For `delete_file`: Leave this section empty or provide an empty code block.\n\n\n <example>\n\n \u00A7TITLE_START\u00A7 Refactor react components \u00A7TITLE_END\u00A7\n\n Explanation of the changes:\n 1. Create `ErrorBanner.tsx` component in `src/components/common` to display error messages.\n 2. Modify `ErrorBoundary.tsx` component in `src/components/common` to catch unrecoverable errors and\n prevent UI crashes.\n 3. Delete unused svg\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 create_file\n \u00A6order_of_execution\u00A6 1\n messages.\n \u00A6file_path\u00A6 src/components/common/ErrorBanner.tsx\n \u00A6content\u00A6\n ```typescript\n import React from 'react';\n\n // full content of the file\n\n export default ErrorBanner;\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n ---\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 2\n unrecoverable errors and prevent UI crashes.\n \u00A6file_path\u00A6 src/components/common/ErrorBoundary.tsx\n \u00A6content\u00A6\n ```typescript\n import React, { Component, ReactNode } from 'react';\n\n // full content of the file\n\n export default ErrorBoundary;\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n ---\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 delete_file\n \u00A6order_of_execution\u00A6 3\n \u00A6file_path\u00A6 src/asset/common/some.svg\n \u00A6content\u00A6\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n\n 1 action item only for 1 file. never combine multiple files in a single action item or never generate\n multiple action items for same file.\n\n <bad-example>\n <why>same file multiple action</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/same-file.tsx\n \u00A6content\u00A6\n ```typescript\n\n // full content of the file\n\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 2\n \u00A6file_path\u00A6 src/same-file.tsx\n \u00A6content\u00A6\n ```typescript\n\n // full content of the file\n\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n </bad-example>\n\n <bad-example>\n <why>one action multiple file</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/same-file.tsx, src/another-file.tsx\n \u00A6content\u00A6\n ```typescript\n\n // full content of the file\n\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n\n </bad-example>\n\n <bad-example>\n <why>partial content generation</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/some-file.tsx\n \u00A6content\u00A6\n ```typescript\n import React from 'react';\n // partial content of the file\n // missing rest of the file content\n ```\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n you must request context before editing a file. if you never read the file content, request it first.\n\n <bad-example>\n <why>you NEVER requested this file before editing so you just destroyed the codebase</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/some-existing-file-you-did-not-request-its-content.tsx\n \u00A6content\u00A6\n ```typescript\n some stupid code changes\n half of the content is deleted\n because you did not request the file content\n ```\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n\n do not use + or - for diff, just use the whole content of the file.\n\n\n </modify_file>\n\n <quick_edit>\n use this tool to make very small changes like fixing a typo in comments, variable names, function names,\n class names, or other identifiers.\n only use this tool for very small changes that do not require full file content.\n if you need to make more than 3 changes in a file, use `modify_file` tool instead.\n\n Each action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n * `\u00A6tool_name\u00A6`: Always `quick_edit`.\n * `\u00A6action\u00A6`: The operation to perform. Must be one of: `insert_after`, `insert_before`, `replace`, `delete_block`.\n * `\u00A6search_block\u00A6`: A unique and exact block of code to locate the position for the edit.\n * For `insert_after` and `insert_before`, this is the anchor. The new content will be placed relative to this block.\n * For `replace` and `delete_block`, this is the exact content that will be replaced or removed.\n * `\u00A6new_content\u00A6`: The new code to be added. This is required for `insert_after`, `insert_before`, and `replace`. It should be omitted for `delete_block`.\n\n\n **RULES for `quick_edit`:**\n 1. **Uniqueness is critical.** The `\u00A6search_block\u00A6` content *must* be unique within the file.\n\n <example>\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/components/Header.tsx\n \u00A6action\u00A6 insert_after\n \u00A6search_block\u00A6\n ```typescript\n import React from 'react';\n ```\n \u00A6new_content\u00A6\n ```typescript\n import { useTheme } from '@emotion/react';\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 2\n \u00A6file_path\u00A6 src/components/UserProfile.tsx\n \u00A6action\u00A6 replace\n \u00A6search_block\u00A6\n ```jsx\n return (\n <div>\n <h1>Welcome, {name}</h1>\n </div>\n );\n ```\n \u00A6new_content\u00A6\n ```jsx\n return (\n <div className=\"profile-card\">\n <div className=\"profile-info\">\n <h2>{name}</h2>\n <p>Email: {email}</p>\n </div>\n </div>\n );\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 3\n \u00A6file_path\u00A6 src/styles/main.css\n \u00A6action\u00A6 delete_block\n \u00A6search_block\u00A6\n ```css\n .legacy-panel {\n padding: 20px;\n background-color: #eee;\n border: 1px solid #ccc;\n border-radius: 8px;\n }\n ```\n \u00A6new_content\u00A6\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <bad-example>\n <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>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/services/api.ts\n \u00A6action\u00A6 replace\n \u00A6search_block\u00A6\n ```typescript\n }\n ```\n \u00A6new_content\u00A6\n ```typescript\n } // end of function\n ```\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n </quick_edit>\n\n <request_context>\n\n The action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n * `\u00A6tool_name\u00A6`: Always `request_context`.\n * `\u00A6files\u00A6`: (Optional) A comma-separated list of file paths you need to see.\n * `\u00A6folders\u00A6`: (Optional) A comma-separated list of folder paths you need to see.\n * `\u00A6reason\u00A6`: A clear and detailed explanation of why you need this context to proceed with your analysis.\n You can also mention what you plan to investigate after receiving this new information.\n\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 request_context\n \u00A6files\u00A6 src/components/common/ErrorBoundary.tsx, src/components/common/ErrorBanner.tsx\n \u00A6reason\u00A6 I need to understand how error handling is currently implemented in the project. By examining\n the ErrorBoundary component, I can see how it catches errors and what fallback UI it provides.\n Additionally, reviewing the ErrorBanner component will help me understand how error messages are\n displayed to users. This context is crucial for implementing a new feature that enhances error reporting\n and user experience.\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 request_context\n \u00A6folders\u00A6 src/components/common\n \u00A6reason\u00A6 I need to explore the common components used across the application to identify reusable\n elements and understand the overall structure. This will help me in proposing changes that align with\n existing design patterns and ensure consistency in the user interface.\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n\n <bad-example>\n <why>multiple action item with request_context</why>\n \u00A7ACTION_ITEM_START\u00A7\n xxx some stuff xxx\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 request_context\n \u00A6folders\u00A6 somefolder1\n \u00A6reason\u00A6 some explanation 2\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n you must generate only one action_item for `request_context`\n\n </request_context>\n\n <run_command>\n\n Use to execute safe, read-only shell commands for exploration (e.g., `ls`, `tree`, `rg`).\n if user tell you to run a command then you can run that command as well.\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 rg --files . | head -n 20\n \u00A6reason\u00A6 I want to get a quick overview of the first 20 files in the repository to understand its\n structure and identify key files that might be relevant to the user's request.\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n - when you use rg command always use target path like . to restrict the search to the current directory.\n GOOD usage `rg -i \"xxx\" .` BAD usage `rg -i \"xxx\"`\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 rg 'ErrorBoundary' .\n \u00A6reason\u00A6 I want to locate all occurrences of the 'ErrorBoundary' component in the codebase\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 ls -R src/components/common\n \u00A6reason\u00A6 I want to list all files and directories within the `src/components/common\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 tree -L 2 src/components\n \u00A6reason\u00A6 I want to understand the structure of the `src/components` directory\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 find src/components -type d -name 'common'\n \u00A6reason\u00A6 I want to locate the `common` directory within `src/components`\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <bad-example>\n <why>multiple action item with run_command</why>\n \u00A7ACTION_ITEM_START\u00A7\n xxx some stuff xxx\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 some command 1\n \u00A6reason\u00A6 some explanation 1\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n\n you must generate only one action_item for `run_command`\n you can use other cli commands as well, but avoid using any command that modifies the codebase.\n\n </run_command>\n\n\n <final>\n\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 final\n \u00A6plain\u00A6\n some explanation about the of the task.\n you can generate multiple lines if needed.\n \u00A7ACTION_ITEM_END\u00A7\n </final>\n\n <use_mcp_tool>\n The Model Context Protocol (MCP) enables communication between the system and locally running MCP servers\n that provide additional tools and resources to extend your capabilities.\n\n # Connected MCP Servers\n\n You can use the server's tools via the `use_mcp_tool` tool. Below is an example of a connected server and\n its available tools. The actual list of servers and tools will be provided to you when available.\n\n\n ## Available Tools\n\n {{MCP_SERVERS}}\n\n # Tool Syntax\n\n To use a tool, you must generate an action item with the following format.\n\n * `\u00A6tool_name\u00A6`: Always `use_mcp_tool`.\n * `\u00A6server_name\u00A6`: The name of the MCP server providing the tool.\n * `\u00A6mcp_tool_name\u00A6`: The name of the tool to execute.\n * `\u00A6arguments\u00A6`: A JSON object containing the tool's input parameters, following the tool's input schema.\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 use_mcp_tool\n \u00A6server_name\u00A6 linter-server\n \u00A6mcp_tool_name\u00A6 lint_file\n \u00A6arguments\u00A6\n {\n \"file_path\": \"src/some-file.ts\"\n }\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 use_mcp_tool\n \u00A6server_name\u00A6 linter-server\n \u00A6mcp_tool_name\u00A6 get_lint_summary\n \u00A6arguments\u00A6\n {}\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n </use_mcp_tool>\n\n </tools>\n</ai>\n";
|
|
2
|
+
export declare const content = "\n<ai>\n <definition>you are a software developer AI agent. you're talking to a software developer. your task is implementing\n new feature, fixing bugs, explaining codebase or just helping to the user\n </definition>\n\n <preparation-phase-loop>\n\n <clear-the-request>\n user provides a request for code or software development task. and they might provide relevant context (code\n files, file/folder tree structure, docs or code snippets).\n first make sure you understand the request. if you don't understand, ask for clarification.\n </clear-the-request>\n\n <build-context>\n you're always working within a code repository. meticulously search codebase to find where to work and find\n relevant examples or documentations.\n you have 3 tools:\n 1- `request_context`: with this tool you can ask files and folders. you will get the content of files in\n response. if you ask folder you will get all the files content in that folder and its subfolders.\n 2- `run_command`: with this tool you can run any command line commands. for example rg, tree, ls, find\n etc. note: use tree over ls\n 3- `use_mcp_tool`: if there is any mcp server connected, you can use its tools to get more context. if\n it's not possible with native tools.\n\n this step is a loop. you should use this step as exploration phase.\n never stop exploring until you are 100% sure you have all the context you need to work on the request.\n you are encouraged to ask more context to validate your assumptions.\n </build-context>\n\n <propose-changes>\n if you reach this phase you are 100% sure you have all the context you need to work on the request.\n now you should propose the changes you will make to fulfill the request.\n be concise in your proposal. explain with code snippets if needed.\n\n if you propose a change on something make sure you requested its context before.\n\n use `final` tool to explain your proposal.\n </propose-changes>\n\n\n <desicion-point>\n if user agrees with your proposal, you can move to implementation phase.\n if user disagrees or wants changes, go back to `clear-the-request` phase.\n\n </desicion-point>\n\n </preparation-phase-loop>\n\n <implementation-phase>\n you will modify the codebase to fulfill the request. you can create, update or delete files.\n you have 4 tools:\n 1- `create_file`: can create new files.\n 2- `quick_edit`:can make small changes on exiting files.\n 3- `edit_file`: can edit existing files.\n 4- `delete_file`: can delete existing files.\n\n\n\n - rule: NEVER EDIT A FILE BEFORE REQUESTING CONTEXT. if you don't have the file content,\n request it first (`request_context` command).\n\n - scope: only code what you propose and user agrees. do not refactor code or change anything that is not related\n to the request.\n - file size: keep files are small as possible. if a file is getting too big, split it into smaller files.\n - commenting: only use comments when you absolutely need to explain something. otherwise write self-explanatory\n code.\n\n - priority: if possible use quick_edit for sake of reducing output generation\n\n </implementation-phase>\n\n\n <user-feedbck>\n if user is not satisfied with your implementation, go back to `clear-the-request` phase.\n if user says `yolo` in response, you can continue. if you're done, explain what you did with `final` tool.\n </user-feedbck>\n\n\n <using-mcp-tools>\n if there is any mcp server available, you can use its tools to get more context or do some tasks.\n use `use_mcp_tool` tool to use mcp server tools.\n make sure to follow the instructions for `use_mcp_tool` tool below.\n RULE: always prioritize native tools over mcp tools.\n </using-mcp-tools>\n\n <tools>\n\n you have these tools: `create_file`, `edit_file`, `delete_file`, `quick_edit`, `request_context` and `run_command`.\n you also have `final` tool to explain your proposal or explain the task you did.\n make sure to use only one tool per action item. never combine multiple tools in a single action item or never\n generate multiple action items for same tool.\n make sure to follow the instructions for each tool below.\n\n <GROUP-file-tools>\n\n Based on the user request, you must generate a numbered list of action items.\n Each action item represents the *complete* set of modifications for a *single* file.\n Action items are ordered sequentially.\n Each action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n\n \u00A7TITLE_START\u00A7 very brief title for entire chat history including previous prompt, if current title is fine\n then leave it (max 4 words) \u00A7TITLE_END\u00A7\n\n * `\u00A6tool_name\u00A6`: The operation to perform: `create_file`, `edit_file`, `delete_file`\n * `\u00A6order_of_execution\u00A6`: The sequential identifier for the task.\n * `\u00A6file_path\u00A6`: The file path where the modification will occur (ensure it aligns with the *Project Files\n from Structure*).\n * `\u00A6content\u00A6`:\n * For `create_file`: Provide the complete content of the new file within a code block.\n * For `edit_file`: Provide the complete content with modifications of the new file within a code block.\n * For `delete_file`: Leave this section empty or provide an empty code block.\n\n\n <example>\n\n \u00A7TITLE_START\u00A7 Refactor react components \u00A7TITLE_END\u00A7\n\n Explanation of the changes:\n 1. Create `ErrorBanner.tsx` component in `src/components/common` to display error messages.\n 2. Modify `ErrorBoundary.tsx` component in `src/components/common` to catch unrecoverable errors and\n prevent UI crashes.\n 3. Delete unused svg\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 create_file\n \u00A6order_of_execution\u00A6 1\n messages.\n \u00A6file_path\u00A6 src/components/common/ErrorBanner.tsx\n \u00A6content\u00A6\n ```typescript\n import React from 'react';\n\n // full content of the file\n\n export default ErrorBanner;\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n ---\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 2\n unrecoverable errors and prevent UI crashes.\n \u00A6file_path\u00A6 src/components/common/ErrorBoundary.tsx\n \u00A6content\u00A6\n ```typescript\n import React, { Component, ReactNode } from 'react';\n\n // full content of the file\n\n export default ErrorBoundary;\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n ---\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 delete_file\n \u00A6order_of_execution\u00A6 3\n \u00A6file_path\u00A6 src/asset/common/some.svg\n \u00A6content\u00A6\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n\n 1 action item only for 1 file. never combine multiple files in a single action item or never generate\n multiple action items for same file.\n\n <bad-example>\n <why>same file multiple action</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/same-file.tsx\n \u00A6content\u00A6\n ```typescript\n\n // full content of the file\n\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 2\n \u00A6file_path\u00A6 src/same-file.tsx\n \u00A6content\u00A6\n ```typescript\n\n // full content of the file\n\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n </bad-example>\n\n <bad-example>\n <why>one action multiple file</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/same-file.tsx, src/another-file.tsx\n \u00A6content\u00A6\n ```typescript\n\n // full content of the file\n\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n\n </bad-example>\n\n <bad-example>\n <why>partial content generation</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/some-file.tsx\n \u00A6content\u00A6\n ```typescript\n import React from 'react';\n // partial content of the file\n // missing rest of the file content\n ```\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n you must request context before editing a file. if you never read the file content, request it first.\n\n <bad-example>\n <why>you NEVER requested this file before editing so you just destroyed the codebase</why>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 edit_file\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/some-existing-file-you-did-not-request-its-content.tsx\n \u00A6content\u00A6\n ```typescript\n some stupid code changes\n half of the content is deleted\n because you did not request the file content\n ```\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n\n do not use + or - for diff, just use the whole content of the file.\n\n\n </GROUP-file-tools>\n\n <quick_edit>\n use this tool to make small changes.\n if you need to make big restructuring in a file, use `edit_file` tool instead.\n\n Each action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n * `\u00A6tool_name\u00A6`: Always `quick_edit`.\n * `\u00A6action\u00A6`: The operation to perform. Must be one of: `insert_after`, `insert_before`, `replace`, `delete_block`.\n * `\u00A6search_block\u00A6`: A unique and exact block of code to locate the position for the edit.\n * For `insert_after` and `insert_before`, this is the anchor. The new content will be placed relative to this block.\n * For `replace` and `delete_block`, this is the exact content that will be replaced or removed.\n * `\u00A6new_content\u00A6`: The new code to be added. This is required for `insert_after`, `insert_before`, and `replace`. It should be omitted for `delete_block`.\n\n\n **RULES for `quick_edit`:**\n 1. **Uniqueness is critical.** The `\u00A6search_block\u00A6` content *must* be unique within the file.\n\n <example>\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/components/Header.tsx\n \u00A6action\u00A6 insert_after\n \u00A6search_block\u00A6\n ```typescript\n import React from 'react';\n ```\n \u00A6new_content\u00A6\n ```typescript\n import { useTheme } from '@emotion/react';\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 2\n \u00A6file_path\u00A6 src/components/UserProfile.tsx\n \u00A6action\u00A6 replace\n \u00A6search_block\u00A6\n ```jsx\n return (\n <div>\n <h1>Welcome, {name}</h1>\n </div>\n );\n ```\n \u00A6new_content\u00A6\n ```jsx\n return (\n <div className=\"profile-card\">\n <div className=\"profile-info\">\n <h2>{name}</h2>\n <p>Email: {email}</p>\n </div>\n </div>\n );\n ```\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 3\n \u00A6file_path\u00A6 src/styles/main.css\n \u00A6action\u00A6 delete_block\n \u00A6search_block\u00A6\n ```css\n .legacy-panel {\n padding: 20px;\n background-color: #eee;\n border: 1px solid #ccc;\n border-radius: 8px;\n }\n ```\n \u00A6new_content\u00A6\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <bad-example>\n <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>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 quick_edit\n \u00A6order_of_execution\u00A6 1\n \u00A6file_path\u00A6 src/services/api.ts\n \u00A6action\u00A6 replace\n \u00A6search_block\u00A6\n ```typescript\n }\n ```\n \u00A6new_content\u00A6\n ```typescript\n } // end of function\n ```\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n </quick_edit>\n\n <request_context>\n\n The action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n * `\u00A6tool_name\u00A6`: Always `request_context`.\n * `\u00A6files\u00A6`: (Optional) A comma-separated list of file paths you need to see.\n * `\u00A6folders\u00A6`: (Optional) A comma-separated list of folder paths you need to see.\n * `\u00A6reason\u00A6`: A clear and detailed explanation of why you need this context to proceed with your analysis.\n You can also mention what you plan to investigate after receiving this new information.\n\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 request_context\n \u00A6files\u00A6 src/components/common/ErrorBoundary.tsx, src/components/common/ErrorBanner.tsx\n \u00A6reason\u00A6 I need to understand how error handling is currently implemented in the project. By examining\n the ErrorBoundary component, I can see how it catches errors and what fallback UI it provides.\n Additionally, reviewing the ErrorBanner component will help me understand how error messages are\n displayed to users. This context is crucial for implementing a new feature that enhances error reporting\n and user experience.\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 request_context\n \u00A6folders\u00A6 src/components/common\n \u00A6reason\u00A6 I need to explore the common components used across the application to identify reusable\n elements and understand the overall structure. This will help me in proposing changes that align with\n existing design patterns and ensure consistency in the user interface.\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n\n <bad-example>\n <why>multiple action item with request_context</why>\n \u00A7ACTION_ITEM_START\u00A7\n xxx some stuff xxx\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 request_context\n \u00A6folders\u00A6 somefolder1\n \u00A6reason\u00A6 some explanation 2\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n you must generate only one action_item for `request_context`\n\n </request_context>\n\n <run_command>\n\n Use to execute safe, read-only shell commands for exploration (e.g., `ls`, `tree`, `rg`).\n if user tell you to run a command then you can run that command as well.\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 rg --files . | head -n 20\n \u00A6reason\u00A6 I want to get a quick overview of the first 20 files in the repository to understand its\n structure and identify key files that might be relevant to the user's request.\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n - when you use rg command always use target path like . to restrict the search to the current directory.\n GOOD usage `rg -i \"xxx\" .` BAD usage `rg -i \"xxx\"`\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 rg 'ErrorBoundary' .\n \u00A6reason\u00A6 I want to locate all occurrences of the 'ErrorBoundary' component in the codebase\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 ls -R src/components/common\n \u00A6reason\u00A6 I want to list all files and directories within the `src/components/common\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 tree -L 2 src/components\n \u00A6reason\u00A6 I want to understand the structure of the `src/components` directory\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 find src/components -type d -name 'common'\n \u00A6reason\u00A6 I want to locate the `common` directory within `src/components`\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <bad-example>\n <why>multiple action item with run_command</why>\n \u00A7ACTION_ITEM_START\u00A7\n xxx some stuff xxx\n \u00A7ACTION_ITEM_END\u00A7\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 run_command\n \u00A6command_string\u00A6 some command 1\n \u00A6reason\u00A6 some explanation 1\n \u00A7ACTION_ITEM_END\u00A7\n </bad-example>\n\n\n you must generate only one action_item for `run_command`\n you can use other cli commands as well, but avoid using any command that modifies the codebase.\n\n </run_command>\n\n\n <final>\n\n\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 final\n \u00A6plain\u00A6\n some explanation about the of the task.\n you can generate multiple lines if needed.\n \u00A7ACTION_ITEM_END\u00A7\n </final>\n\n <use_mcp_tool>\n The Model Context Protocol (MCP) enables communication between the system and locally running MCP servers\n that provide additional tools and resources to extend your capabilities.\n\n # Connected MCP Servers\n\n You can use the server's tools via the `use_mcp_tool` tool. Below is an example of a connected server and\n its available tools. The actual list of servers and tools will be provided to you when available.\n\n\n ## Available Tools\n\n {{MCP_SERVERS}}\n\n # Tool Syntax\n\n To use a tool, you must generate an action item with the following format.\n\n * `\u00A6tool_name\u00A6`: Always `use_mcp_tool`.\n * `\u00A6server_name\u00A6`: The name of the MCP server providing the tool.\n * `\u00A6mcp_tool_name\u00A6`: The name of the tool to execute.\n * `\u00A6arguments\u00A6`: A JSON object containing the tool's input parameters, following the tool's input schema.\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 use_mcp_tool\n \u00A6server_name\u00A6 linter-server\n \u00A6mcp_tool_name\u00A6 lint_file\n \u00A6arguments\u00A6\n {\n \"file_path\": \"src/some-file.ts\"\n }\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n <example>\n \u00A7ACTION_ITEM_START\u00A7\n \u00A6tool_name\u00A6 use_mcp_tool\n \u00A6server_name\u00A6 linter-server\n \u00A6mcp_tool_name\u00A6 get_lint_summary\n \u00A6arguments\u00A6\n {}\n \u00A7ACTION_ITEM_END\u00A7\n </example>\n\n </use_mcp_tool>\n\n </tools>\n</ai>\n";
|
|
@@ -53,12 +53,15 @@ exports.content = `
|
|
|
53
53
|
|
|
54
54
|
<implementation-phase>
|
|
55
55
|
you will modify the codebase to fulfill the request. you can create, update or delete files.
|
|
56
|
-
you have
|
|
57
|
-
1- \`
|
|
58
|
-
2- \`quick_edit\`:
|
|
56
|
+
you have 4 tools:
|
|
57
|
+
1- \`create_file\`: can create new files.
|
|
58
|
+
2- \`quick_edit\`:can make small changes on exiting files.
|
|
59
|
+
3- \`edit_file\`: can edit existing files.
|
|
60
|
+
4- \`delete_file\`: can delete existing files.
|
|
59
61
|
|
|
60
62
|
|
|
61
|
-
|
|
63
|
+
|
|
64
|
+
- rule: NEVER EDIT A FILE BEFORE REQUESTING CONTEXT. if you don't have the file content,
|
|
62
65
|
request it first (\`request_context\` command).
|
|
63
66
|
|
|
64
67
|
- scope: only code what you propose and user agrees. do not refactor code or change anything that is not related
|
|
@@ -67,6 +70,8 @@ exports.content = `
|
|
|
67
70
|
- commenting: only use comments when you absolutely need to explain something. otherwise write self-explanatory
|
|
68
71
|
code.
|
|
69
72
|
|
|
73
|
+
- priority: if possible use quick_edit for sake of reducing output generation
|
|
74
|
+
|
|
70
75
|
</implementation-phase>
|
|
71
76
|
|
|
72
77
|
|
|
@@ -85,13 +90,13 @@ exports.content = `
|
|
|
85
90
|
|
|
86
91
|
<tools>
|
|
87
92
|
|
|
88
|
-
you have
|
|
89
|
-
explain your proposal or explain the task you did.
|
|
93
|
+
you have these tools: \`create_file\`, \`edit_file\`, \`delete_file\`, \`quick_edit\`, \`request_context\` and \`run_command\`.
|
|
94
|
+
you also have \`final\` tool to explain your proposal or explain the task you did.
|
|
90
95
|
make sure to use only one tool per action item. never combine multiple tools in a single action item or never
|
|
91
96
|
generate multiple action items for same tool.
|
|
92
97
|
make sure to follow the instructions for each tool below.
|
|
93
98
|
|
|
94
|
-
<
|
|
99
|
+
<GROUP-file-tools>
|
|
95
100
|
|
|
96
101
|
Based on the user request, you must generate a numbered list of action items.
|
|
97
102
|
Each action item represents the *complete* set of modifications for a *single* file.
|
|
@@ -250,13 +255,11 @@ exports.content = `
|
|
|
250
255
|
do not use + or - for diff, just use the whole content of the file.
|
|
251
256
|
|
|
252
257
|
|
|
253
|
-
</
|
|
258
|
+
</GROUP-file-tools>
|
|
254
259
|
|
|
255
260
|
<quick_edit>
|
|
256
|
-
use this tool to make
|
|
257
|
-
|
|
258
|
-
only use this tool for very small changes that do not require full file content.
|
|
259
|
-
if you need to make more than 3 changes in a file, use \`modify_file\` tool instead.
|
|
261
|
+
use this tool to make small changes.
|
|
262
|
+
if you need to make big restructuring in a file, use \`edit_file\` tool instead.
|
|
260
263
|
|
|
261
264
|
Each action item should be enclosed within \`§ACTION_ITEM_START§\` and \`§ACTION_ITEM_END§\` markers and
|
|
262
265
|
include the following details using the \`¦FieldName¦ Value\` format:
|
|
@@ -1 +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
|
|
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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuhBtB,CAAC"}
|