CCAR-F practice › Claude Code Configuration & Workflows · Question 64 of 105
Claude Code Configuration & Workflows · Select TWO
Your CI job invokes Claude Code to review pull requests. The job sometimes hangs until it times out, and when it does finish, the pipeline struggles to turn the free-form review text into inline PR comments. Which two changes address these problems? Select two.
Show answer and explanation
Answer: B and D — Run Claude Code with the -p flag so that it runs non-interactively and then exits / Use --output-format json with --json-schema so findings follow a defined shape
-p (--print) runs Claude Code in non-interactive mode, so it processes the prompt, prints the result, and exits instead of waiting for input. --output-format json with --json-schema produces machine-parseable findings in a defined structure that the pipeline can post as inline comments. (A) works around the hang instead of using non-interactive mode. (C) breaks whenever the wording changes.
Keep going
More Claude Code Configuration & Workflows questions
- Your CI review runs on every push to a pull request. Developers complain that each push…
- In your pipeline, the Claude Code session that implements a fix is then asked to review…
- 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…