Profile My skills Saved Collections Edit profile Submit a skill

Gitvow Trace

When a code region looks surprising or unfamiliar, find who wrote each line, agent or person, in which session and step, with the stated plan. Use for "what happened here", "who wrote this", or before deleting code whose purpose is unclear.

wirevow 058817b 1.0 KB Updated
AI & ML

File contents

Who wrote these lines?

Run:

gitvow trace <path>:<start>-<end>     # a range
gitvow trace <path>                   # the whole file

Each line group shows agent with the session, step and the plan stated at the time, or person with the commit. Ranges are grouped by commit so a mixed region reads as a sequence of authorship.

How to use the answer:

  • Lines by a person after an agent session are the human's decision; preserve their intent.
  • An agent plan that does not mention the region is a signal the lines were incidental; check gitvow why <path> for the wider story before changing them.
  • To see the exact file the agent produced at that step, list gitvow snapshots --session <id> and use gitvow diff <id> <n> or gitvow restore <id> <n>.

wirevow/gitvow-skills/tree/main/skills/gitvow-trace commit 058817bdce

Browse category

Frequently asked questions

npx skillmds@latest add wirevow/gitvow-trace