You are integrating Claude Code into your Continuous Integration/Continuous Deployment (CI/CD) pipeline. The system runs automated code reviews, generates test cases, and provides feedback on pull requests. You need to design prompts that provide actionable feedback and minimize false positives.

Your pipeline runs: ``` PROMPT="You are a code reviewer."

PROMPT="$PROMPT Analyze the provided diff"

PROMPT="$PROMPT for bugs, security issues,"

PROMPT="$PROMPT and style violations." claude -p \ -- dangerously-skip-permissions \ --system-prompt "$PROMPT" \ < diff.txt``` The reviews complete and return feedback, but Claude only comments on the piped diff text – it never reads surrounding files in the checked-out repository to understand broader context, even when the diff modifies a function called by many other modules.

Which change to the invocation will cause Claude to read related files in the repository while still applying your custom review instructions?