From 8faaadf53737bffd6088ade9eda93908cff0f2cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kacper=20Miko=C5=82ajczak?= Date: Mon, 23 Mar 2026 11:35:18 +0100 Subject: [PATCH] Instruct reviewer to use bare script name for compiler check The allowedTools pattern Bash(check-compiler.sh:*) only matches when the command starts with the bare script name. The reviewer LLM resolves to absolute paths (/home/runner/.../check-compiler.sh), causing permission denials. Add an explicit instruction to the rule to use the script by name only since it is already on $PATH. --- .claude/skills/coding-standards/rules/clean-react-0-compiler.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.claude/skills/coding-standards/rules/clean-react-0-compiler.md b/.claude/skills/coding-standards/rules/clean-react-0-compiler.md index c2a5283346b94..67dfc4692b8d3 100644 --- a/.claude/skills/coding-standards/rules/clean-react-0-compiler.md +++ b/.claude/skills/coding-standards/rules/clean-react-0-compiler.md @@ -101,6 +101,8 @@ Before flagging, verify that the file actually compiles with React Compiler: check-compiler.sh ``` +**IMPORTANT:** Run `check-compiler.sh` exactly as shown above - by name only, without an absolute path or `bash` prefix. The script is already on `$PATH`. + If the output contains **"Failed to compile"** for the file under review, the rule **does not apply** — the author may have no alternative to manual memoization until the compilation issue is resolved. #### Condition