Ticket Trace

Two operations that share one idea: a commit message is the join key between code and the reason for the code. Writing commits without a ticket number breaks the chain; answering "why" questions without following the chain to the ticket produces guesses.

The chain

code line → git blame/log → commit → ticket number in message → ticket in tracker → reason (text + ATTACHED IMAGES)

Real example that motivated this skill: a hardcoded label looked like a naming bug. git log -S "Vehicles" → commit e40eb36 "fix 5887" → ADO ticket #5887 → the description was one annotated screenshot saying "Rename Auto to Vehicles / Hide Breakbulk". The hardcode was an explicit requirement. Without opening the image, the answer would have been wrong.

Operation A — Commit with a ticket number

Every commit in a ticketed repo must reference its ticket. Resolve the number in this order, and say which source you used: