chromatic-setup-ci
Chromatic CI Setup
Set up Chromatic visual testing automation in CI/CD pipelines.
This skill is the single source of truth for:
- detecting which CI provider the project uses
- fetching the current Chromatic docs for that provider
- generating CI configuration files for Chromatic
- setting up the project token secret
Quick start
- Read
reference/ci-detection.mdto identify the CI provider from existing config files. - If no CI config is found, ask the user which CI provider they use.
- Read
reference/package-manager.mdand detect the package manager from lockfiles. - Look up the provider's docs URL in
reference/docs-map.mdand fetch it with WebFetch. - For non-GitHub-Actions providers: check
package.jsonfor achromaticdevDependency and script — add them if missing. Skip this step for GitHub Actions. - Generate or update the CI configuration using the fetched docs and the detected package manager.
- Render the setup checklist using
reference/output-contract.md.
More from chromaui/chromatic-skills
turbosnap-debug
Diagnose TurboSnap behavior using logs, config, git context, support-shareable hosted metadata references, and targeted trace commands. Use when you need to classify why TurboSnap is enabled, disabled, unavailable, or tracing the wrong stories, then recommend the smallest valid next step.
8chromatic-themes
Configure Chromatic to capture visual test snapshots across multiple themes (light/dark mode, design tokens, branded variants) using the Modes API and @storybook/addon-themes. Use when the user wants to test components with different themes in Chromatic, set up light/dark mode visual testing, configure @storybook/addon-themes with Chromatic, or apply theme modes at the project, component, or story level.
6chromatic-viewports
Configure Chromatic to capture visual test snapshots at multiple viewport sizes using the Modes API. Use when the user wants to test responsive components at different screen sizes, set up viewport breakpoints for Chromatic visual testing, apply viewports to individual stories or globally, control snapshot height with cropToViewport, or migrate from the legacy chromatic.viewports API to the new Modes API.
6chromatic-troubleshoot-config
Diagnose Storybook configuration issues that block Chromatic or local Storybook, including missing stories, framework or builder mismatches, addon conflicts, preview errors, static asset path issues, and package version drift. Use when Storybook fails to build, Chromatic cannot verify Storybook, stories are missing, or a team needs the smallest config change to restore a working Storybook surface.
6chromatic-turbosnap-debug
Diagnose TurboSnap behavior using logs, config, git context, support-shareable hosted metadata references, and targeted trace commands. Use when you need to classify why TurboSnap is enabled, disabled, unavailable, or tracing the wrong stories, then recommend the smallest valid next step.
6chromatic-workflow-debug
Diagnose Chromatic workflow issues involving git history, baselines, pull request event shape, merge queues, merge-base failures, replacement builds, and patch builds. Use when builds compare against the wrong baseline, an ancestor build is not found, pull request comparisons look wrong, or CI git context does not match Chromatic's expectations.
5