Claude Code for Continuous Integration
Your CI pipeline uses Claude Code to generate automated code review summaries for pull requests. After three weeks in production, developers report that roughly 12% of summaries contain specific claims about code behavior — such as "this function will throw a NullPointerException when input is null" — that don't match what the code actually does. Logs show the review agent is being passed only the diff and a generic instruction to summarize changes. Which prompt engineering change would most directly reduce this category of hallucinated behavioral claims?