The scenario
The repository has a test framework and an existing reproduction supplied with this task.
Required context: a selected repository matching this scenario, relevant task evidence, and access to its instructions and checks. Use redacted or synthetic data where appropriate.
Adapt the complete prompt
Edits stay in this browser tab. Saving bookmarks the original example; export your edited version to keep it elsewhere.
Why this is a strong example
It demands a discriminating failure before the fix, which is stronger than adding a permanently green test afterwards.
A concrete outcome
Create a focused failing test for the reported bug before changing the implementation.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Inspect nearby tests and follow their conventions. Make the test fail for the reported behavior, not an unrelated setup error. Preserve current assertions.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Show the failing case on the original code, then implement the narrow fix and show the same test passing with relevant existing checks.
These checks describe what would make acceptance justified; asking for them does not mean they ran.
A safe way to encounter uncertainty
If the repository contradicts these assumptions, required access is unavailable, or a consequential product decision is missing, explain the conflict and pause the dependent work. Preserve unrelated changes.
Consequential uncertainty stays visible rather than being converted into an invented requirement.