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
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ This will start a web server for the AgentTide UI. Follow the on-screen instruct
83
83
84
84
**Usage Tips:**
85
85
If you know the exact code context, specify identifiers directly in your request (e.g., `module.submodule.file_withoutextension.object`).
86
-
You can request a plan, edit steps, and proceed step-by-step—see the [chainlit.md](codetide/agents/tide/ui/chainlit.md) for full details and advanced workflows!
86
+
You can use the `plan` command to generate a step-by-step implementation plan for your request, review and edit the plan, and then proceed step-by-step. The `commit` command allows you to review and finalize changes before they are applied. See the [chainlit.md](codetide/agents/tide/ui/chainlit.md) for full details and advanced workflows, including the latest specifications for these commands!
Copy file name to clipboardExpand all lines: codetide/agents/tide/prompts.py
+26-7Lines changed: 26 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -258,6 +258,8 @@
258
258
259
259
FINAL CHECKLIST BEFORE PATCHING:
260
260
261
+
0. Ensure you have all the required context to generate the patch, if you feel like something is missing ask the user for clarification:
262
+
- it is preferable to ask for clarification instead of halucinating a patch without enough context.
261
263
1. Validate that every line you edit exists exactly as-is in the original context
262
264
2. Ensure one patch block per file, using multiple @@ hunks as needed
263
265
3. Include no formatting, layout, or interpretation changes
@@ -274,9 +276,7 @@
274
276
275
277
Your job is to take a user request, analyze any provided code context (including repository structure / repo_tree identifiers), and decompose the work into the minimal set of concrete implementation steps needed to fully satisfy the request.
276
278
If the requirement is simple, output a single step; if it’s complex, decompose it into multiple ordered steps. You must build upon, refine, or correct any existing code context rather than ignoring it.
277
-
If the user provides feedback on prior steps, update the current steps to reflect that feedback. If the user responds “all is good” or equivalent, do not repeat the steps—reply exactly with:
278
-
279
-
<START_CODING>
279
+
If the user provides feedback on prior steps, update the current steps to reflect that feedback. If the user responds “all is good” or equivalent, do not repeat the steps - ask the user if he wants you to start implementing them one by one in sequence.
280
280
281
281
Important Note:
282
282
If the user's request already contains a complete step, is direct enough to be solved without additional decomposition, or does not require implementation planning at all (e.g., general questions, documentation requests, commit messages), you may skip the multi-step planning and execution mode entirely.
@@ -320,16 +320,16 @@
320
320
321
321
10. **Succinctness of Format:** Strictly adhere to the step formatting with separators (`---`) and the beginning/end markers. Do not add extraneous numbering or narrative outside the prescribed structure.
322
322
323
-
When the user confirms everything is correct and no further planning is needed, respond only with:
324
-
325
-
<START_CODING>
326
-
327
323
---
328
324
329
325
`repo_tree`
330
326
{REPO_TREE}
331
327
"""
332
328
329
+
CMD_TRIGGER_PLANNING_STEPS="""
330
+
331
+
"""
332
+
333
333
CMD_WRITE_TESTS_PROMPT="""
334
334
Analyze the provided code and write comprehensive tests.
335
335
Ensure high coverage by including unit, integration, and end-to-end tests that address edge cases and follow best practices.
@@ -343,4 +343,23 @@
343
343
CMD_COMMIT_PROMPT="""
344
344
Generate a conventional commit message that summarizes the work done since the previous commit.
345
345
The message should have a clear subject line and a body explaining the problem solved and the implementation approach.
346
+
347
+
Important Instructions:
348
+
349
+
Place the commit message inside exactly this format:
350
+
*** Begin Commit
351
+
[commit message]
352
+
*** End Commit
353
+
354
+
You may include additional comments about the changes made outside of this block
355
+
356
+
If no diffs for staged files are provided in the context, reply that there's nothing to commit
357
+
358
+
The commit message should follow conventional commit format with a clear type/scope prefix
359
+
"""
360
+
361
+
STAGED_DIFFS_TEMPLATE="""
362
+
** The following diffs are currently staged and will be commited once you generate an appropriate description:**
0 commit comments