book_appointment go up after the model upgrade?” This page covers what Triggers compares and how to go from a change to the commit behind it.
When to use
What Triggers Compares
Triggers compares a metric across model versions or user segments and shows when it changes.Example Prompts
“Did the Misstep rate on book_appointment go up after the model upgrade?”
“Compare the Exception rate by model version for traces in the last 30 days”
From a Change to a Commit
The/kubit-blame skill in Claude Code or Cursor finds the commits most likely to have caused a trace regression. It maps agent names, tool names and prompts from the traces to files in your repo, then ranks commits in the time window by how close they are in time, how much of the mapped code they touch and how large the change is. It returns the top 5 suspect commits. Find what changed before a pattern started walks through it.
Related
- Flows: the execution paths whose numbers Triggers compares.
- Find what changed before a pattern started: the steps from a regression to a commit.
- Kubit Skills: the full
/kubit-blamereference.