메뉴
Use when working in Windows terminals where `rg` may resolve to an inaccessible bundled binary. Apply whenever searching files or text with ripgrep (`rg`, `rg --files`, `rg -n`) to force resolution of the machine-local rg.exe path and execute ripgrep by absolute path.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | windows-rg-path |
| description | Use when working in Windows terminals where `rg` may resolve to an inaccessible bundled binary. Apply whenever searching files or text with ripgrep (`rg`, `rg --files`, `rg -n`) to force resolution of the machine-local rg.exe path and execute ripgrep by absolute path. |
目标：在 Windows 下优先使用机器上独立可访问的 rg.exe，避免误用 Codex 内置的 WindowsApps 路径。
在当前任务第一次调用 ripgrep 前，先解析路径：
(Get-Command rg).Source
如果解析结果指向：
C:\Program Files\WindowsApps\OpenAI.Codex_...\app\resources\rg.exe
就把它视为 Codex 内置二进制，不要作为首选 rg。
如果路径为空、命中内置路径、或调用失败，就执行：
where.exe rg
选择第一个不在 WindowsApps\OpenAI.Codex_ 下的有效 .exe 路径。
一旦找到独立版 rg.exe，后续调用都使用绝对路径执行，例如：
& 'C:\Program Files\PowerShell\7\rg.exe' --files
& 'C:\Program Files\PowerShell\7\rg.exe' 'pattern' -n .
如果绝对路径执行报错（例如 access denied），立即退回 PowerShell 原生搜索，不要卡住任务。
不要假设 alias 或 shell 状态能跨工具调用保留；每次都按“新 shell”处理。
如果找不到可用的独立版 rg.exe，或者绝对路径执行失败，就直接改用 PowerShell 原生搜索：
Get-ChildItem -Recurse -File
Get-ChildItem -Recurse -File | Select-String -Pattern 'keyword'
rg 路径WindowsApps\OpenAI.Codex_...\resources\rg.exerg.exeUse when Codex on Windows needs to connect to a locally reachable MySQL or PostgreSQL database. Apply for client detection, PATH repair, connectivity validation, read-only SQL execution, and socket 10106 troubleshooting that may require bypassing the shell network stack with Node REPL MCP.
Use when writing, refactoring, reviewing, or documenting code where comments should be improved. Prefer structured, intent-focused comments with Chinese business-context style when appropriate, including section headers for major phases, professional tags for risks/performance/business constraints, Javadoc for public methods in Controller/Service/ServiceImpl classes, and concise call-site notes before important private helper method calls inside long public methods. Avoid noisy comments that only repeat syntax.
Use when writing, refactoring, reviewing, or modernizing Java code that should target Java 8 style. Prefer safe IntelliJ IDEA inspection suggestions and Java 8 idioms such as Map.computeIfAbsent, getOrDefault, removeIf, streams for clear transformations, method references, Optional where it improves null-handling, and String.trim().isEmpty() over length checks. Avoid overusing Optional, streams, or clever one-liners when plain code is clearer.