repoburg 1.1.9 → 1.1.10
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/backend/dist/src/ai-actions/ai-action-creation.service.d.ts +1 -0
- package/backend/dist/src/ai-actions/ai-action-creation.service.js +34 -0
- package/backend/dist/src/ai-actions/ai-action-creation.service.js.map +1 -1
- package/backend/dist/src/ai-actions/ai-actions.service.d.ts +1 -0
- package/backend/dist/src/ai-actions/ai-actions.service.js +1 -0
- package/backend/dist/src/ai-actions/ai-actions.service.js.map +1 -1
- package/backend/dist/src/core-entities/ai-action.entity.d.ts +1 -0
- package/backend/dist/src/core-entities/ai-action.entity.js +4 -0
- package/backend/dist/src/core-entities/ai-action.entity.js.map +1 -1
- package/backend/dist/src/llm-response-parser/dto/ai-action.dto.d.ts +4 -1
- package/backend/dist/src/llm-response-parser/dto/ai-action.dto.js +17 -0
- package/backend/dist/src/llm-response-parser/dto/ai-action.dto.js.map +1 -1
- package/backend/dist/src/llm-response-parser/llm-response-parser.service.js +4 -0
- package/backend/dist/src/llm-response-parser/llm-response-parser.service.js.map +1 -1
- package/backend/dist/src/llm-response-parser/parsing.constants.d.ts +1 -0
- package/backend/dist/src/llm-response-parser/parsing.constants.js +2 -1
- package/backend/dist/src/llm-response-parser/parsing.constants.js.map +1 -1
- package/backend/dist/src/llm-responses/llm-responses.service.d.ts +4 -1
- package/backend/dist/src/llm-responses/llm-responses.service.js +49 -2
- package/backend/dist/src/llm-responses/llm-responses.service.js.map +1 -1
- package/backend/dist/src/seeding/data/context-templates/default-followup_ad-hoc-focused-context.d.ts +1 -1
- package/backend/dist/src/seeding/data/context-templates/default-followup_ad-hoc-focused-context.js +0 -1
- package/backend/dist/src/seeding/data/context-templates/default-followup_ad-hoc-focused-context.js.map +1 -1
- package/backend/dist/src/seeding/data/context-templates/default-initial_full-project-context.d.ts +1 -1
- package/backend/dist/src/seeding/data/context-templates/default-initial_full-project-context.js +2 -41
- package/backend/dist/src/seeding/data/context-templates/default-initial_full-project-context.js.map +1 -1
- package/backend/dist/src/seeding/data/context-templates/open-pr-command.d.ts +1 -1
- package/backend/dist/src/seeding/data/context-templates/open-pr-command.js +1 -1
- package/backend/dist/src/seeding/data/context-templates/open-pr-command.js.map +1 -1
- package/backend/dist/src/seeding/data/system-prompts/carryover-agent.d.ts +2 -0
- package/backend/dist/src/seeding/data/system-prompts/carryover-agent.js +107 -0
- package/backend/dist/src/seeding/data/system-prompts/carryover-agent.js.map +1 -0
- package/backend/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +1 -1
- package/backend/dist/src/seeding/data/context-templates/pm-context.d.ts +0 -2
- package/backend/dist/src/seeding/data/context-templates/pm-context.js +0 -59
- package/backend/dist/src/seeding/data/context-templates/pm-context.js.map +0 -1
- package/backend/dist/src/seeding/data/context-templates/sample_focused-tree.d.ts +0 -2
- package/backend/dist/src/seeding/data/context-templates/sample_focused-tree.js +0 -15
- package/backend/dist/src/seeding/data/context-templates/sample_focused-tree.js.map +0 -1
package/package.json
CHANGED
|
@@ -1,2 +0,0 @@
|
|
|
1
|
-
export declare const template_name = "PM Context";
|
|
2
|
-
export declare const template_content = "You are an AI assistant. You will be provided with several context sections, each clearly marked by unique delimiters. Your primary and most important goal is to understand and fulfill the request detailed in the \"MY_REQUEST\" section.\n\nThe context sections are structured as follows:\n- Content between \"%%%%BEGIN_SECTION_CODEBASE%%%%\" and \"%%%%END_SECTION_CODEBASE%%%%\" contains the relevant codebase or code snippets.\n- Content between \"%%%%BEGIN_SECTION_DOCS%%%%\" and \"%%%%END_SECTION_DOCS%%%%\" contains documentation, specifications, or explanatory material.\n- Content between \"%%%%BEGIN_SECTION_GENERAL_RULES%%%%\" and \"%%%%END_SECTION_GENERAL_RULES%%%%\" contains general rules, constraints, or guidelines that MUST be followed.\n- Content between \"%%%%BEGIN_SECTION_MY_REQUEST%%%%\" and \"%%%%END_SECTION_MY_REQUEST%%%%\" is my specific request or question.\n\nPRIORITIZATION AND CONFLICT RESOLUTION:\n1. **MY_REQUEST:** This section is paramount. All your efforts should be directed towards satisfying this request.\n2. **GENERAL_RULES:** These rules are mandatory and must be adhered to when formulating your response and fulfilling MY_REQUEST. If a GENERAL_RULE seems to conflict with information in DOCS or CODEBASE, the GENERAL_RULE takes precedence. If MY_REQUEST explicitly asks to override or ignore a specific rule for a particular instance, you may do so, but clearly state that you are deviating from a general rule due to the explicit request.\n3. **CODEBASE:** This is the primary source material for any tasks involving code analysis, modification, or generation, as guided by MY_REQUEST and constrained by GENERAL_RULES.\n4. **DOCS:** This section provides supplementary information. Use it to understand concepts, APIs, or background related to the CODEBASE or MY_REQUEST. If information in DOCS conflicts with CODEBASE (e.g., outdated docs), generally trust the CODEBASE unless MY_REQUEST or GENERAL_RULES suggest otherwise.\n\nWhen processing, carefully parse each section according to these delimiters. If you encounter any ambiguity or direct contradiction that prevents fulfilling MY_REQUEST while adhering to GENERAL_RULES, please state the conflict and, if possible, suggest a resolution or ask for clarification.\n\nNow, here is the context:\n\n%%%%BEGIN_SECTION_CODEBASE%%%%\n\n<%~ await it.tree('--gitignore -I \"node_modules|dist|coverage\"') %>\n\n<%~ await it.ripGrep('--heading \"\" . -g \"!*.md\"') %>\n\n%%%%END_SECTION_CODEBASE%%%%\n\n%%%%BEGIN_SECTION_DOCS%%%%\n<%~ await it.ripGrep('--heading \"\" .repoburg/docs') %>\n%%%%END_SECTION_DOCS%%%%\n\n\n%%%%BEGIN_SECTION_GENERAL_RULES%%%%\n\n- do not generate code\n- just write task specifications\n\n%%%%END_SECTION_GENERAL_RULES%%%%\n\n\n%%%%BEGIN_SECTION_SELECTED_FILES%%%%\n<%~ it.adhoc_files_content %>\n\n<%~ it.adhoc_folders_content %>\n%%%%END_SECTION_SELECTED_FILES%%%%\n\n\n\n%%%%BEGIN_SECTION_MY_REQUEST%%%%\n\nfollow SECTION_GENERAL_RULES (do not generate code, just write task specifications)\n\n<%~ it.user_input %>\n\n%%%%END_SECTION_MY_REQUEST%%%%";
|
|
@@ -1,59 +0,0 @@
|
|
|
1
|
-
"use strict";
|
|
2
|
-
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
|
-
exports.template_content = exports.template_name = void 0;
|
|
4
|
-
exports.template_name = 'PM Context';
|
|
5
|
-
exports.template_content = `You are an AI assistant. You will be provided with several context sections, each clearly marked by unique delimiters. Your primary and most important goal is to understand and fulfill the request detailed in the "MY_REQUEST" section.
|
|
6
|
-
|
|
7
|
-
The context sections are structured as follows:
|
|
8
|
-
- Content between "%%%%BEGIN_SECTION_CODEBASE%%%%" and "%%%%END_SECTION_CODEBASE%%%%" contains the relevant codebase or code snippets.
|
|
9
|
-
- Content between "%%%%BEGIN_SECTION_DOCS%%%%" and "%%%%END_SECTION_DOCS%%%%" contains documentation, specifications, or explanatory material.
|
|
10
|
-
- Content between "%%%%BEGIN_SECTION_GENERAL_RULES%%%%" and "%%%%END_SECTION_GENERAL_RULES%%%%" contains general rules, constraints, or guidelines that MUST be followed.
|
|
11
|
-
- Content between "%%%%BEGIN_SECTION_MY_REQUEST%%%%" and "%%%%END_SECTION_MY_REQUEST%%%%" is my specific request or question.
|
|
12
|
-
|
|
13
|
-
PRIORITIZATION AND CONFLICT RESOLUTION:
|
|
14
|
-
1. **MY_REQUEST:** This section is paramount. All your efforts should be directed towards satisfying this request.
|
|
15
|
-
2. **GENERAL_RULES:** These rules are mandatory and must be adhered to when formulating your response and fulfilling MY_REQUEST. If a GENERAL_RULE seems to conflict with information in DOCS or CODEBASE, the GENERAL_RULE takes precedence. If MY_REQUEST explicitly asks to override or ignore a specific rule for a particular instance, you may do so, but clearly state that you are deviating from a general rule due to the explicit request.
|
|
16
|
-
3. **CODEBASE:** This is the primary source material for any tasks involving code analysis, modification, or generation, as guided by MY_REQUEST and constrained by GENERAL_RULES.
|
|
17
|
-
4. **DOCS:** This section provides supplementary information. Use it to understand concepts, APIs, or background related to the CODEBASE or MY_REQUEST. If information in DOCS conflicts with CODEBASE (e.g., outdated docs), generally trust the CODEBASE unless MY_REQUEST or GENERAL_RULES suggest otherwise.
|
|
18
|
-
|
|
19
|
-
When processing, carefully parse each section according to these delimiters. If you encounter any ambiguity or direct contradiction that prevents fulfilling MY_REQUEST while adhering to GENERAL_RULES, please state the conflict and, if possible, suggest a resolution or ask for clarification.
|
|
20
|
-
|
|
21
|
-
Now, here is the context:
|
|
22
|
-
|
|
23
|
-
%%%%BEGIN_SECTION_CODEBASE%%%%
|
|
24
|
-
|
|
25
|
-
<%~ await it.tree('--gitignore -I "node_modules|dist|coverage"') %>
|
|
26
|
-
|
|
27
|
-
<%~ await it.ripGrep('--heading "" . -g "!*.md"') %>
|
|
28
|
-
|
|
29
|
-
%%%%END_SECTION_CODEBASE%%%%
|
|
30
|
-
|
|
31
|
-
%%%%BEGIN_SECTION_DOCS%%%%
|
|
32
|
-
<%~ await it.ripGrep('--heading "" .repoburg/docs') %>
|
|
33
|
-
%%%%END_SECTION_DOCS%%%%
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
%%%%BEGIN_SECTION_GENERAL_RULES%%%%
|
|
37
|
-
|
|
38
|
-
- do not generate code
|
|
39
|
-
- just write task specifications
|
|
40
|
-
|
|
41
|
-
%%%%END_SECTION_GENERAL_RULES%%%%
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
%%%%BEGIN_SECTION_SELECTED_FILES%%%%
|
|
45
|
-
<%~ it.adhoc_files_content %>
|
|
46
|
-
|
|
47
|
-
<%~ it.adhoc_folders_content %>
|
|
48
|
-
%%%%END_SECTION_SELECTED_FILES%%%%
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
%%%%BEGIN_SECTION_MY_REQUEST%%%%
|
|
53
|
-
|
|
54
|
-
follow SECTION_GENERAL_RULES (do not generate code, just write task specifications)
|
|
55
|
-
|
|
56
|
-
<%~ it.user_input %>
|
|
57
|
-
|
|
58
|
-
%%%%END_SECTION_MY_REQUEST%%%%`;
|
|
59
|
-
//# sourceMappingURL=pm-context.js.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"pm-context.js","sourceRoot":"","sources":["../../../../../src/seeding/data/context-templates/pm-context.ts"],"names":[],"mappings":";;;AAAa,QAAA,aAAa,GAAG,YAAY,CAAC;AAC7B,QAAA,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;+BAqDD,CAAC"}
|
|
@@ -1,2 +0,0 @@
|
|
|
1
|
-
export declare const template_name = "General: Focused Tree";
|
|
2
|
-
export declare const template_content = "User Request:\n<%~ it.user_input %>\n\n---\n### Context\n\n#### Project Structure (Focused)\n```\n<%~ await it.tree('-L 2 --gitignore -I \"node_modules|dist|coverage\"') %>\n```";
|
|
@@ -1,15 +0,0 @@
|
|
|
1
|
-
"use strict";
|
|
2
|
-
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
|
-
exports.template_content = exports.template_name = void 0;
|
|
4
|
-
exports.template_name = 'General: Focused Tree';
|
|
5
|
-
exports.template_content = `User Request:
|
|
6
|
-
<%~ it.user_input %>
|
|
7
|
-
|
|
8
|
-
---
|
|
9
|
-
### Context
|
|
10
|
-
|
|
11
|
-
#### Project Structure (Focused)
|
|
12
|
-
\`\`\`
|
|
13
|
-
<%~ await it.tree('-L 2 --gitignore -I "node_modules|dist|coverage"') %>
|
|
14
|
-
\`\`\``;
|
|
15
|
-
//# sourceMappingURL=sample_focused-tree.js.map
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"sample_focused-tree.js","sourceRoot":"","sources":["../../../../../src/seeding/data/context-templates/sample_focused-tree.ts"],"names":[],"mappings":";;;AAAa,QAAA,aAAa,GAAG,uBAAuB,CAAC;AACxC,QAAA,gBAAgB,GAAG;;;;;;;;;OASzB,CAAC"}
|