git-audit

name	git-audit
description	Investigate history with log/blame/search and produce actionable findings.
compatibility	opencode
metadata	{"workflow":"git","audience":"engineers"}

What I do

• Answer “when/why was this changed?” and “who introduced this?”
• Find commits by content, not just filenames.
• Produce reproducible command sequences for the user.

When to use me

• You’re debugging a regression.
• You need the commit that introduced/removed a behavior.
• You want to understand ownership and intent.

Workflow toolbox

• Recent history:
  • git log --oneline --decorate -20
• File history:
  • git log --follow -- <path>
• Who touched this line:
  • git blame -L <start>,<end> <path>
• Search by added/removed text:
  • git log -S "<literal>" --oneline
  • git log -G "<regex>" --oneline
• Inspect a commit:
  • git show <sha>

Guardrails

• Prefer read-only commands.
• If suggesting git bisect, confirm the user can run tests locally.

Bisect (when tests exist)

1. git bisect start
2. git bisect bad
3. git bisect good <known-good-sha>
4. Iterate until culprit commit found
5. git bisect reset

Output expectations

• Provide the exact command(s) to reproduce the finding.
• Provide the suspect commit SHA(s) and subject lines.