Chromatic

Plugin chromatic from marketplace chromatic in chromaui/chromatic-plugins. Commands read from the repo's manifest — 6 days ago.

Skills (13)

• address-review-feedback

  Reads the open reviewer comment threads on a Chromatic build, maps each one to its story and component, makes the changes the reviewers asked for, and drafts a reply for each thread. Use when a Chromatic build has comments or discussions, when a reviewer left feedback on snapshots, or when the user

• check-merge-readiness

  Says whether a branch is ready to merge from Chromatic's side, by checking its latest build against the current commit, broken and denied tests, changes still waiting for review, open reviewer comments and new accessibility violations, and lists what is left. Use when the user asks if their branch o

• check-project-setup

  Checks that this repository is connected to the right Chromatic project and that the project is set up to test it, by comparing the project's framework, linked repository, enabled features and recent builds with the repository's own config, CI and git remote. Use when the user asks whether Chromatic

• connect-project

  Finds which Chromatic project this repository belongs to with a read-only lookup from the git remote, then records the id in chromatic.config.json so every Chromatic tool knows which project to ask about. Use before asking the user for a project id, whenever a Chromatic tool needs a projectId and ch

• find-existing-component

  Before building a new UI component, checks the repository and the project's published Storybook on Chromatic for one that already does the job, and reports the closest matches with links to their stories. Use when the user asks for a new component, asks whether one already exists ("do we have a date

• fix-accessibility-violations

  Finds the accessibility violations a Chromatic build reported, fixes them in the component source, and verifies the fix on the next build. Use when a Chromatic build reports accessibility changes, when CI fails on a11y, or when the user asks which stories have accessibility violations or got worse,

• fix-broken-stories

  Finds the stories a Chromatic build could not capture, reads each capture error (render and interaction timeouts, JavaScript errors, failed play functions, missing or off-page stories, oversized snapshots), fixes the cause in the repository, and verifies on the next build. Use when a Chromatic build

• get-latest-build

  Reports the latest Chromatic build for this repository's project, on the current branch unless another is named. Use when the user asks what Chromatic thinks of their branch, whether the build passed or is still running, for the build id the accessibility tools need, or right after a push to see whe

• query-chromatic

  Answers questions about Chromatic data with a read-only GraphQL query, such as a build by its number, the tests on a build by status, how many tests are pending or broken, which Chromatic user is signed in, reviewer comments, quarantined stories, or the components in a published Storybook. Use befor

• reduce-snapshot-usage

  Shows where a Chromatic project's snapshots go, by component, story, mode and browser, and proposes story parameter changes that cut them without losing coverage the team relies on. Use when the user asks why Chromatic uses so many snapshots, how many snapshots the project uses, how to lower the bil

• review-visual-changes

  Reviews the visual changes a Chromatic build is waiting on, compares each changed snapshot with the code change on the branch, and shows the person which changes look intended and which look like regressions, with before, after and diff pictures. Use right after you push or open a pull request that

• run-build

  Runs a Chromatic build from this machine with the Chromatic CLI, limited to the stories being worked on, waits for the result, and reports it, so a fix can be verified without pushing and waiting for CI. Use when the user asks to run Chromatic, to verify a fix on Chromatic now, or to check why Turbo

• triage-flaky-stories

  Lists a Chromatic project's quarantined stories and the tests a build ignored as unstable, finds what makes each story render differently from run to run, and fixes the cause in the story or component. Use when the user asks about flaky, unstable or quarantined stories in Chromatic, asks to quaranti

MCP servers (1)

• chromatic

  connects to: https://mcp.chromatic.com/mcp

Similar plugins