Question 1 · choose 1
Your CI reviewer writes a markdown summary for each pull request. The instructions ask for the location, the issue, a severity and a suggested fix for every finding, yet some findings lack line numbers, severities vary in wording, and fixes are sometimes missing. Which change most reliably makes the findings consistent?
- AAdd a few example findings to the prompt, each written in the exact format
- BSet the temperature to 0 so that every finding comes out in the same format each time the review runs
- CRepeat the format requirements in capital letters at both the start and the end of the instructions
- DAsk Claude to check its findings against the format rules before finishing
Show the answer and why
AAdd a few example findings to the prompt, each written in the exact format
Correct
Examples are one of the most reliable ways to steer output format; they show the structure the instructions only describe.
BSet the temperature to 0 so that every finding comes out in the same format each time the review runs
Incorrect
Lower randomness does not teach the format; it can make the same inconsistent layout repeat more reliably.
CRepeat the format requirements in capital letters at both the start and the end of the instructions
Incorrect
Repetition and emphasis do not show what a correct finding looks like, so the variation continues.
DAsk Claude to check its findings against the format rules before finishing
Incorrect
A self-check against rules it already misapplies is weaker than a concrete pattern to copy.
When detailed instructions alone give inconsistent formatting, add a few targeted examples of the exact output. Few-shot examples demonstrate the format in a way prose cannot.
Anthropic documentation