Your CI pipeline performs security-focused code reviews on approximately 50 pull requests daily, currently costing $150 per day through the synchronous API. Reviews are non-blocking-- developers merge after tests pass and address findings in follow-up commits. You are evaluating the Message Batches API because it offers a 50% cost reduction. What factor most determines whether batch processing is appropriate for this use case?

• A. Whether your result-processing system can handle reviews arriving in a different order from the order in which they were submitted.
• B. Whether each review can be structured as a single request without multi-turn refinement.
• C. Whether review feedback arriving up to 24 hours after pull-request creation remains actionable.
• D. Whether reducing per-review latency from 30?0 seconds to near-instantaneous delivery matters to your workflow.

You are building developer productivity tools using the Claude Agent SDK. The agent helps engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate code, and automate repetitive tasks. It uses the built-in tools (Read, Write, Bash, Grep, Glob) and integrates with Model Context Protocol (MCP) servers.
Your agent has spent 25 minutes exploring a game engine's rendering subsystem -reading shader code, buffer management, and frame synchronization logic. An engineer now asks it to understand how the physics engine integrates with rendering for collision debug overlays. You notice recent responses reference "typical rendering patterns" rather than the specific VulkanPipeline and FrameGraph classes it discovered earlier.
What's the most effective approach?

• A. Summarize key rendering findings, then spawn a sub-agent for physics exploration with that summary in its initial context.
• B. Continue in the current context with more targeted prompts referencing the specific classes by name.
• C. Use /clear to reset context completely, then start fresh with physics exploration using file paths from the project's CLAUDE.md.
• D. Spawn a sub-agent to explore physics independently, then manually synthesize its findings with the rendering knowledge accumulated in the main conversation.

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.
After deploying automated code review, developers report that approximately 35% of findings are false positives following consistent patterns: style suggestions that contradict team conventions, security warnings for patterns that are safe in the deployment environment, and performance suggestions that would degrade this particular use case.
You want to reduce false positives while enabling the model to generalize its judgment to novel code patterns it has not seen before.
Which approach is most effective?

• A. Use keyword-based post-processing to remove findings containing terms such as "convention,"
  "context-dependent," or "trade-off."
• B. Create a comprehensive specification of every pattern that must not be flagged and include the complete document in the system prompt.
• C. Add general instructions telling Claude to be conservative and report only definite issues.
• D. Include few-shot examples containing annotated code snippets that distinguish acceptable project patterns from genuine issues in each category.

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 comments only on the piped diff--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 repository files while still applying your custom review instructions?

• A. Remove --system-prompt entirely and place the review instructions in a root-level CLAUDE.md because --system-prompt is incompatible with tool use under -p.
• B. Keep --system-prompt and add --allowedTools "Read, Glob, Grep" because non-interactive -p mode otherwise disables filesystem tools.
• C. Stop piping the diff through standard input and embed it in the prompt string so Claude Code treats the invocation as an agentic session rather than a stream-processing operation.
• D. Replace --system-prompt with --append-system-prompt so the review instructions are added to Claude Code's default prompt instead of overwriting its built-in file-reading and code-navigation guidance.

You are building developer productivity tools using the Claude Agent SDK. The agent helps engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate code, and automate repetitive tasks. It uses the built-in tools (Read, Write, Bash, Grep, Glob) and integrates with Model Context Protocol (MCP) servers.
An engineer asks your agent to add comprehensive tests to a legacy codebase with 200 files and minimal existing test coverage. The engineer hasn't specified which modules to prioritize.
How should the agent decompose this open-ended task?

• A. Use Glob and Grep to map codebase structure, identify heavily-coupled modules, create a prioritized plan for high-impact areas, and revise as dependencies are discovered.
• B. Systematically read all 200 files to create a complete function inventory before writing any tests, ensuring the testing plan accounts for every function before beginning.
• C. Create a fixed testing schedule upfront based on directory structure, allocating equal effort to each top-level directory regardless of code complexity or business importance.
• D. Start writing tests for the first module alphabetically, using test failures and imports to discover related files organically.