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
- You MUST use `safeWriteJson(filePath: string, data: any): Promise<void>` from `src/utils/safeWriteJson.ts` instead of `JSON.stringify` with file-write operations
4
+
-`safeWriteJson` will create parent directories if necessary, so do not call `mkdir` prior to `safeWriteJson`
5
+
-`safeWriteJson` prevents data corruption via atomic writes with locking and streams the write to minimize memory footprint
Copy file name to clipboardExpand all lines: .roo/rules-pr-reviewer/1_workflow.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@
100
100
</arguments>
101
101
</use_mcp_tool>
102
102
103
-
Examine existing PR comments to understand the current state of discussion. Always verify whether a comment is current or already addressed before suggesting action.
103
+
Examine existing PR comments to understand the current state of discussion. When reading the comments and reviews, you must verify which are resolved by reading the files they refer to, since they might already be resolved. This prevents you from making redundant suggestions.
Copy file name to clipboardExpand all lines: .roo/rules-translate/001-general-rules.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,8 +64,10 @@
64
64
1. Identify where the string appears in the UI/codebase
65
65
2. Understand the context and purpose of the string
66
66
3. Update English translation first
67
-
4. Create appropriate translations for all other supported languages
68
-
5. Validate your changes with the missing translations script
67
+
4. Use the `<search_files>` tool to find JSON keys that are near new keys in English translations but do not yet exist in the other language files for `<apply_diff>` SEARCH context
68
+
5. Create appropriate translations for all other supported languages utilizing the `search_files` result using `<apply_diff>` without reading every file.
69
+
6. Do not output the translated text into the chat, just modify the files.
70
+
7. Validate your changes with the missing translations script
69
71
- Flag or comment if an English source string is incomplete ("please see this...") to avoid truncated or unclear translations
70
72
- For UI elements, distinguish between:
71
73
- Button labels: Use short imperative commands ("Save", "Cancel")
0 commit comments