# Investigate a repository behavior

Investigate [behavior or failure] in [repository]. Reproduction information: [inputs, environment, expected result, observed result].

Locate the relevant entry point, follow the data and state changes, and use file references to explain the cause. Read additional files when they resolve a concrete uncertainty. Distinguish what the code proves from what still requires execution.

Propose the smallest coherent correction and identify affected callers. If this request also authorizes implementation, make that correction and verify the relevant flow. Preserve unrelated changes.

Return the cause, the evidence, the correction or proposal, and the checks actually completed. Do not report every repository tool as tested after sampling one flow.