Investigate Git History

Objective

Produce an evidence-backed history explanation with exact commits, paths, ranges, and limitations.

Use When

• Find the commit that added, removed, renamed, or changed specific text or behavior.
• Trace a path across renames or inspect merge ancestry and first-parent history.
• Explain who last changed lines while accounting for moves, copies, or generated code.
• Compare whether a patch was applied, reverted, or independently recreated.

Do Not Use / Route Elsewhere

• Use find-regression when a reproducible good/bad test can locate a causal boundary.
• Use a dedicated SWE review workflow to assess correctness of a proposed diff.
• Use recover-lost-work when the goal is to restore missing objects.
• Do not alter refs, files, or remote state.