[NoQA] Fix reviewer using absolute paths for compiler check script

[kacper-mikolajczak]

Explanation of Change

Background: PR #85067 added check-compiler.sh to the reviewer's allowedTools so the CLEAN-REACT-PATTERNS-0 rule could verify React Compiler compliance before flagging manual memoization. The script is on $PATH (via $GITHUB_PATH) and the allowed pattern is Bash(check-compiler.sh:*).

Problem: After analyzing post-merge reviewer runs (e.g. PRs #85636, #85629), the compiler check is never executing successfully. The reviewer LLM resolves the script to its absolute path (/home/runner/_work/App/App/.claude/scripts/check-compiler.sh ...) or prefixes it with bash. Since Bash(check-compiler.sh:*) is prefix-matched against the literal command string, these invocations don't match and are permission-denied. The reviewer retries up to 4+ times with different path variants before giving up.

This is the same class of issue that previously affected createInlineComment.sh and addPrReaction.sh (resolved in #83651 by moving script execution to the workflow level via structured JSON output).

Solution: Add an explicit instruction in the CLEAN-REACT-PATTERNS-0 rule telling the reviewer to invoke check-compiler.sh by bare name only - no absolute path, no bash prefix. This is the lightweight fix; if it proves insufficient, a follow-up would pre-compute compiler results at the workflow level.

Fixed Issues

$ #85070
PROPOSAL:

Tests

• Verify that no errors appear in the JS console

1. Open .claude/skills/coding-standards/rules/clean-react-0-compiler.md
2. Verify the Verification section contains: 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.
3. Wait for next reviewer run on a PR that touches files with useMemo/useCallback/React.memo
4. Check the workflow run logs for check-compiler.sh invocations - verify the command uses the bare name (not an absolute path) and is no longer in permission_denials

Offline tests

N/A - changes are to reviewer instructions only, no runtime code affected.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

N/A - this is a CI/tooling change with no user-facing impact. Verification is that the reviewer agent can successfully run the compliance check on future PRs.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[kacper-mikolajczak]

CC @adhorodyski @mountiny

Verified the fix works on a fork test run: https://github.com/kacper-mikolajczak/ExpensifyApp/actions/runs/23434474868

The reviewer now invokes check-compiler.sh by bare name and no longer lands in permission_denials.

Fallback if this doesn't work reliably: Instead of having the reviewer call check-compiler.sh inline, we could pre-compute compiler compliance results at the workflow level (reusing the existing CI compiler check) and write them to a file the reviewer can Read. This would also let us drop the setupNode step from the reviewer workflow entirely - the reviewer agent only needs Read, Grep, Glob, and gh commands, none of which require Node.

[melvin-bot]

@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]