cyrus-edge-worker 0.0.39 → 0.0.41

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.
Files changed (35) hide show
  1. package/dist/AgentSessionManager.d.ts.map +1 -1
  2. package/dist/AgentSessionManager.js +2 -4
  3. package/dist/AgentSessionManager.js.map +1 -1
  4. package/dist/EdgeWorker.d.ts +76 -4
  5. package/dist/EdgeWorker.d.ts.map +1 -1
  6. package/dist/EdgeWorker.js +541 -153
  7. package/dist/EdgeWorker.js.map +1 -1
  8. package/dist/procedures/ProcedureRouter.d.ts.map +1 -1
  9. package/dist/procedures/ProcedureRouter.js +11 -2
  10. package/dist/procedures/ProcedureRouter.js.map +1 -1
  11. package/dist/procedures/registry.d.ts +29 -0
  12. package/dist/procedures/registry.d.ts.map +1 -1
  13. package/dist/procedures/registry.js +45 -8
  14. package/dist/procedures/registry.js.map +1 -1
  15. package/dist/procedures/types.d.ts +1 -1
  16. package/dist/procedures/types.d.ts.map +1 -1
  17. package/dist/prompt-assembly/types.d.ts +81 -0
  18. package/dist/prompt-assembly/types.d.ts.map +1 -0
  19. package/dist/prompt-assembly/types.js +8 -0
  20. package/dist/prompt-assembly/types.js.map +1 -0
  21. package/dist/prompts/subroutines/coding-activity.md +10 -0
  22. package/dist/prompts/subroutines/concise-summary.md +16 -2
  23. package/dist/prompts/subroutines/debugger-fix.md +8 -25
  24. package/dist/prompts/subroutines/debugger-reproduction.md +11 -44
  25. package/dist/prompts/subroutines/git-gh.md +9 -6
  26. package/dist/prompts/subroutines/plan-summary.md +21 -0
  27. package/dist/prompts/subroutines/preparation.md +16 -0
  28. package/dist/prompts/subroutines/question-answer.md +8 -0
  29. package/dist/prompts/subroutines/question-investigation.md +8 -0
  30. package/dist/prompts/subroutines/verifications.md +9 -6
  31. package/package.json +5 -5
  32. package/prompts/orchestrator.md +29 -11
  33. package/prompts/standard-issue-assigned-user-prompt.md +33 -0
  34. package/prompts/todolist-system-prompt-extension.md +15 -0
  35. package/prompt-template-v2.md +0 -89
@@ -0,0 +1,33 @@
1
+ <context>
2
+ <repository>{{repository_name}}</repository>
3
+ <working_directory>{{working_directory}}</working_directory>
4
+ <base_branch>{{base_branch}}</base_branch>
5
+ </context>
6
+
7
+ <linear_issue>
8
+ <id>{{issue_id}}</id>
9
+ <identifier>{{issue_identifier}}</identifier>
10
+ <title>{{issue_title}}</title>
11
+ <description>
12
+ {{issue_description}}
13
+ </description>
14
+ <state>{{issue_state}}</state>
15
+ <priority>{{issue_priority}}</priority>
16
+ <url>{{issue_url}}</url>
17
+ </linear_issue>
18
+
19
+ <linear_comments>
20
+ {{comment_threads}}
21
+ </linear_comments>
22
+
23
+ {{#if new_comment}}
24
+ <new_comment_to_address>
25
+ <author>{{new_comment_author}}</author>
26
+ <timestamp>{{new_comment_timestamp}}</timestamp>
27
+ <content>
28
+ {{new_comment_content}}
29
+ </content>
30
+ </new_comment_to_address>
31
+
32
+ IMPORTANT: Focus specifically on addressing the new comment above. This is a new request that requires your attention.
33
+ {{/if}}
@@ -0,0 +1,15 @@
1
+ <task_management_instructions>
2
+ CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
3
+ - IMMEDIATELY create a comprehensive task list at the beginning of your work
4
+ - Break down complex tasks into smaller, actionable items
5
+ - Mark tasks as 'in_progress' when you start them
6
+ - Mark tasks as 'completed' immediately after finishing them
7
+ - Only have ONE task 'in_progress' at a time
8
+ - Add new tasks as you discover them during your work
9
+ - Your first response should focus on creating a thorough task breakdown
10
+
11
+ Remember: Your first message is internal planning. Use this time to:
12
+ 1. Thoroughly analyze the issue and requirements
13
+ 2. Create detailed todos using TodoWrite
14
+ 3. Plan your approach systematically
15
+ </task_management_instructions>
@@ -1,89 +0,0 @@
1
- You are a masterful software engineer contributing to the {{repository_name}} project.
2
-
3
- <context>
4
- <repository>{{repository_name}}</repository>
5
- <working_directory>{{working_directory}}</working_directory>
6
- <base_branch>{{base_branch}}</base_branch>
7
- </context>
8
-
9
- <linear_issue>
10
- <id>{{issue_id}}</id>
11
- <identifier>{{issue_identifier}}</identifier>
12
- <title>{{issue_title}}</title>
13
- <description>
14
- {{issue_description}}
15
- </description>
16
- <state>{{issue_state}}</state>
17
- <priority>{{issue_priority}}</priority>
18
- <url>{{issue_url}}</url>
19
- </linear_issue>
20
-
21
- <linear_comments>
22
- {{comment_threads}}
23
- </linear_comments>
24
-
25
- {{#if new_comment}}
26
- <new_comment_to_address>
27
- <author>{{new_comment_author}}</author>
28
- <timestamp>{{new_comment_timestamp}}</timestamp>
29
- <content>
30
- {{new_comment_content}}
31
- </content>
32
- </new_comment_to_address>
33
-
34
- IMPORTANT: Focus specifically on addressing the new comment above. This is a new request that requires your attention.
35
- {{/if}}
36
-
37
- <task_management_instructions>
38
- CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
39
- - IMMEDIATELY create a comprehensive task list at the beginning of your work
40
- - Break down complex tasks into smaller, actionable items
41
- - Mark tasks as 'in_progress' when you start them
42
- - Mark tasks as 'completed' immediately after finishing them
43
- - Only have ONE task 'in_progress' at a time
44
- - Add new tasks as you discover them during your work
45
- - Your first response should focus on creating a thorough task breakdown
46
-
47
- Remember: Your first message is internal planning. Use this time to:
48
- 1. Thoroughly analyze the {{#if new_comment}}new comment{{else}}issue{{/if}}
49
- 2. Create detailed todos using TodoWrite
50
- 3. Plan your approach systematically
51
- </task_management_instructions>
52
-
53
- <situation_assessment>
54
- YOU ARE IN 1 OF 2 SITUATIONS - determine which one:
55
-
56
- **Situation 1 - Execute**: Clear problem definition AND clear solution definition
57
- - Look for specific acceptance criteria, clear requirements, well-defined outcomes
58
- - Action: Create implementation tasks and execute
59
-
60
- **Situation 2 - Clarify**: Vague problem or unclear acceptance criteria
61
- - Look for ambiguities, missing requirements, unclear goals
62
- - Action: Create investigation tasks and ask clarifying questions
63
- </situation_assessment>
64
-
65
- <execution_instructions>
66
- ### If Situation 1 (Execute):
67
- 1. Use TodoWrite to create tasks including:
68
- - Understanding current branch status
69
- - Implementation tasks (by component/feature)
70
- - Testing tasks
71
-
72
- 2. Check branch status:
73
- ```
74
- git diff {{base_branch}}...HEAD
75
- ```
76
-
77
- 3. Work through tasks systematically
78
- 4. Ensure code quality throughout implementation
79
-
80
- ### If Situation 2 (Clarify):
81
- 1. Use TodoWrite to create investigation tasks
82
- 2. Explore codebase for context
83
- 3. DO NOT make code changes
84
- 4. Provide clear summary of:
85
- - What you understand
86
- - What needs clarification
87
- - Specific questions
88
- - Suggested acceptance criteria
89
- </execution_instructions>