diagnose-chromatic-baselines
Installation
SKILL.md
Diagnose Chromatic Baselines
Find the first build where the expected baseline stopped carrying forward. Separate confirmed evidence from facts that only Chromatic Support can verify.
Keep the investigation customer-safe
- Work read-only unless the user explicitly requests a review action.
- Use only data the customer owns or can access normally.
- Never request a project token, API secret, session cookie, or signed asset URL in chat.
- Never instruct the user to extract credentials from a browser session.
- Never query an internal Chromatic API or production environment.
- Do not identify a server limit, provider failure, or baseline-selection defect as confirmed without direct evidence.
- Redact customer names, repository names, and committer email addresses from shared reports when they are not required.
Collect the minimum evidence
First distinguish UI Test acceptance from UI Review sign-off. For stacks, merge queues, overlapping builds, or approval timing, read reference/concurrent-builds.md. Start with the provided evidence and ask for one missing artifact at a time.
If an accepted UI Test still appears in the PR's expected UI Review changeset, explain that distinction and stop. Do not collect an ancestry bundle when the evidence already answers the question.