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: docs/basic-usage/context-mentions.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,12 @@ Use the `@problems` mention to include a list of all current errors and warnings
27
27
***Example:** "@problems Fix all errors in the current file."
28
28
***Note:** This is especially useful when you see errors in the Problems panel and want Roo Code to address them.
29
29
30
+
### Terminal Mention (`@terminal`)
31
+
32
+
Use the `@terminal` mention to include the last command run in the terminal along with its output.
33
+
34
+
***Example:** "Fix the warnings in the @terminal."
35
+
30
36
### Git Commit Mentions (`@a1b2c3d`)
31
37
32
38
Use a Git commit hash (short or long) to include information about a specific commit.
@@ -59,4 +65,4 @@ Use a URL to have Roo Code fetch and include the content of a website.
59
65
***Use Relative Paths:** When referring to files within your workspace, use paths relative to the workspace root.
60
66
***Check for Typos:** Make sure the file paths and commit hashes are correct.
61
67
62
-
Context mentions are a powerful tool for providing Roo Code with the information it needs to complete your tasks effectively. Experiment with different types of mentions to see how they can improve your workflow.
68
+
Context mentions are a powerful tool for providing Roo Code with the information it needs to complete your tasks effectively. Experiment with different types of mentions to see how they can improve your workflow.
0 commit comments