You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(plan-parser): simplify plan parsing logic and UI borders #331
- Replace XML `<THOUGHT>` tags with code-fence blocks for plan content.
- Simplify UI borders in `ThoughtPlanSketchProvider` by using `JBUI.Borders.empty()`.
- Refactor `MarkdownPlanParser` to handle flat ordered lists and improve section processing.
- Add test case for parsing markdown with single section and tasks.
Copy file name to clipboardExpand all lines: core/src/main/resources/genius/en/code/plan.devin
+1-13Lines changed: 1 addition & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Here is the rule you should follow:
40
40
41
41
1. Thoroughly review `<user.question>`. Create an initial plan that includes all the necessary steps to
42
42
resolve `<user.question>`, using the recommended steps provided below, and incorporating any requirements from
43
-
the `<user.question>`. Place your plan inside the XML tag `<THOUGHT>` within the code language `plan`.
43
+
the `<user.question>`. Place your plan inside code-fence block which language is `plan`.
44
44
2. Review the project’s codebase, examining not only its structure but also the specific implementation details, to
45
45
identify all segments that may contribute to or help resolve the issue described in `<user.question>`.
46
46
3. If `<user.question>` describes an error, create a script to reproduce it and run the script to confirm the error.
@@ -57,18 +57,6 @@ Here is the rule you should follow:
57
57
If `<user.question>` directly contradicts any of these steps, follow the instructions from `<user.question>`
58
58
first. Be thorough in your thinking process, so it's okay if it is lengthy.
59
59
60
-
For each step, document your reasoning process inside `<THOUGHT>` tags. Include the following information, enclosed within XML tags:
61
-
62
-
1. `plan`: An updated plan incorporating the outcomes from the previous step. Mark progress by adding `✓` after each task in the plan that was fully completed before this step during the **current session**. Use the symbol `!` for tasks that have a latest status as failed, and use `*` for tasks that are currently in progress. If there are sub-tasks, mark their progress statuses as well. Ensure all progress statuses are marked accurately and appropriately reflect the hierarchical relationships of statuses between tasks and sub-tasks. For example, if all sub-tasks are completed, the parent task should also be marked as completed.
Copy file name to clipboardExpand all lines: core/src/main/resources/genius/zh/code/plan.devin
+1-13Lines changed: 1 addition & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Here is the rule you should follow:
40
40
41
41
1. Thoroughly review `<user.question>`. Create an initial plan that includes all the necessary steps to
42
42
resolve `<user.question>`, using the recommended steps provided below, and incorporating any requirements from
43
-
the `<user.question>`. Place your plan inside the XML tag `<THOUGHT>` within the code language `plan`.
43
+
the `<user.question>`. Place your plan inside code-fence block which language is `plan`.
44
44
2. Review the project’s codebase, examining not only its structure but also the specific implementation details, to
45
45
identify all segments that may contribute to or help resolve the issue described in `<user.question>`.
46
46
3. If `<user.question>` describes an error, create a script to reproduce it and run the script to confirm the error.
@@ -57,18 +57,6 @@ Here is the rule you should follow:
57
57
If `<user.question>` directly contradicts any of these steps, follow the instructions from `<user.question>`
58
58
first. Be thorough in your thinking process, so it's okay if it is lengthy.
59
59
60
-
For each step, document your reasoning process inside `<THOUGHT>` tags. Include the following information, enclosed within XML tags:
61
-
62
-
1. `plan`: An updated plan incorporating the outcomes from the previous step. Mark progress by adding `✓` after each task in the plan that was fully completed before this step during the **current session**. Use the symbol `!` for tasks that have a latest status as failed, and use `*` for tasks that are currently in progress. If there are sub-tasks, mark their progress statuses as well. Ensure all progress statuses are marked accurately and appropriately reflect the hierarchical relationships of statuses between tasks and sub-tasks. For example, if all sub-tasks are completed, the parent task should also be marked as completed.
0 commit comments