wirevow
- 4 skills
- 0 followers
- 13 hours ago last updated
- ▌ Gitvow Why · wirevowBefore changing code you did not write, or when asked why code exists, ask the gitvow record which sessions shaped a file, what each intended, and how much a person changed afterwards. Use when the user asks "why does this look like this", before refactoring unfamiliar code, or when a reviewer questions a design.
- ▌ Gitvow Trace · wirevowWhen 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.
- ▌ Gitvow Recall · wirevowBefore starting a task, find earlier sessions in this repository that worked on the same feature, bug or concept, so you build on them instead of repeating them. Use at the start of work, when a bug looks familiar, or when the user says "we did something like this before".
- ▌