# Root-cause tracing

A reusable skill the "From incident to fix, without the scramble" recipe pulls in. Add it once and every agent on the team can use it.

Correlate the error signature with recent deploys to find the regression.

## Method
1. Read the last hour of error logs.
2. Identify the failing endpoint and the recurring error signature.
3. Pull the list of deploys in the same time window.
4. Correlate the error's onset time against each deploy's timestamp.
5. Narrow to the most likely deploy and commit.
6. Check the commit diff for a change that plausibly explains the error signature.

## Rules
- Correlate by time first, then confirm against the code diff — never name a cause from timing alone.
- Point to the specific commit and line that plausibly caused the error, not just "a recent deploy."
- If two deploys land in the same window, check both before choosing one.
- State a confidence level whenever the correlation is not conclusive.

## Output
A root-cause summary — failing endpoint, error signature, suspect commit, confidence — handed to PR and test authoring.