uvcs-root-cause

Trace a bug, regression, crash or failing test back to the UVCS / Plastic SCM changeset that most likely introduced it: bound the history window, expand from the symptom file to what it depends on, rank only changesets with concrete evidence, and confirm the top suspect at line level with cm annotate. Read-only end to end. Use when the user asks why something broke, what changeset or cset broke it, which change introduced a bug, who broke a file or a line, when a feature last worked, how to bisect or blame a regression in UVCS, or hands you a stack trace, error message or failing test and wants the culprit changeset. Not for reviewing what a branch changed and not for performing a merge. All cm syntax comes from the uvcs-core skill — load it first.

Compatibility

Requires the cm CLI (Unity Version Control client) on PATH