CCAR-F practice › Claude Code Configuration & Workflows · Question 66 of 105
Claude Code Configuration & Workflows
In your pipeline, the Claude Code session that implements a fix is then asked to review its own changes before merge. These reviews almost always approve, but human reviewers keep finding bugs afterwards. What is the most effective change?
Show answer and explanation
Answer: C — Review the diff with an independent Claude Code instance, not the generating session
The session that generated the code carries its own reasoning and assumptions, so it tends to confirm its decisions when reviewing them. An independent review instance without that context is more effective at catching what the generator missed. (A), (B), and (D) all keep the review inside the biased session.
Keep going
More Claude Code Configuration & Workflows questions
- A CI job uses Claude Code to generate unit tests for changed modules. Reviewers report…
- A monorepo has one root CLAUDE.md that three package teams keep editing to add build…
- A 1,200-line root CLAUDE.md mixes testing, API, deployment, and frontend standards…
- A new engineer reports that Claude Code ignores the team's API naming conventions in…
- For the same developer on the same branch, Claude follows the repository's logging…