What counts as UI

A pull request is reviewed when it changes at least one UI file. Everything else is skipped with a neutral check and costs nothing.

The gate is a fixed list of file globs, the same in every repository. You can’t add to it, but you can keep paths out of it with a .crocotaste.yml in your repository, which is the one thing there is to configure: it says which files are read, never what they’re checked against, so your design knowledge stays in DESIGN.md.

The file globs

A changed file counts as UI when its path matches one of:

**/*.tsx  **/*.jsx  **/*.vue  **/*.svelte  **/*.astro
**/*.html  **/*.css  **/*.scss  **/*.sass  **/*.less  **/*.mdx
**/*.styles.{ts,js}  **/*.styled.{ts,js}
tailwind.config.{js,cjs,mjs,ts}

Tests and test material do not count either: a *.test.* or *.spec.* file, or anything under test/, tests/, fixtures/, __tests__/, __fixtures__/ or __mocks__/, since a test’s markup is never shipped. Neither does generated output: anything under node_modules/, dist/, .next/, .nuxt/, .svelte-kit/, .turbo/ or coverage/, at any depth. A folder named build/, out/ or vendor/ is still reviewed, since that can be a route or a feature of yours; if yours holds build output or vendored code, add it to .crocotaste.yml. A Storybook story does count, because it is a component your team looks at. Files the pull request deletes do not count. Draft pull requests wait, silently and without a check, until they are marked ready for review.

One matching file is enough. A pull request with 40 backend files and one .css file is reviewed, and only that file’s added lines are looked at, which is why the numbers on the check count UI files rather than changed files.

If nothing matches, the check reads Skipped · no UI files changed in neutral, no comment is posted, and no review is spent. That is the common case for a backend team and it is meant to be free.

Keeping a folder out of review

Some .tsx or .html isn’t your product’s UI: a promo video drawn in React with Remotion, email templates, generated icon components, a vendored widget. Their literal colors are deliberate, and a review of them is noise. List them in a .crocotaste.yml at the root of your repository:

exclude:
  - apps/video # a whole folder, and everything in it
  - packages/emails
  - "**/*.generated.tsx"

A path keeps the whole folder out. A glob takes * (anything inside one folder name), ** (any number of folders) and ? (one character). A pattern with no / matches at any depth, so *.generated.tsx and **/*.generated.tsx are the same. Up to 100 entries, each at most 200 characters; ! patterns aren’t supported. exclude is the only key read.

Crocotaste also honors your .gitattributes: a file marked linguist-generated or linguist-vendored is left out, the same files GitHub already collapses in a diff.

src/generated/** linguist-generated
packages/legacy-widget/** linguist-vendored

An excluded file gets no findings, from the checks or the AI review, and doesn’t count toward the review ceiling. The summary or the check says how many were left out, for example Not reviewed: 3 files excluded by .crocotaste.yml. A pull request whose every UI file is excluded is skipped as Skipped · every UI file excluded, with the count beside it, and spends no review. A finding already posted on a file you exclude later stays where it is and is never marked fixed, since nothing re-checked it.

Both files are read from the pull request’s own head commit when its branch is in your repository and its author can push to it, so the pull request that adds .crocotaste.yml is already covered by it. A pull request from a fork, or from someone who can’t push to the repository, has them read from the base commit instead, even after a member asks for the review, so a contributor can’t exclude their own changes; a fork’s new .crocotaste.yml applies once it’s merged. If .crocotaste.yml can’t be read (it isn’t valid YAML, it’s over 16 KB, or exclude isn’t a list of paths), the review goes ahead as if the file weren’t there and the summary says so.

What your design system is read from

Crocotaste reads your system at the pull request’s base commit, so a change to DESIGN.md inside a pull request never judges that same pull request. It reads DESIGN.md at the repository root, or docs/DESIGN.md when there is no root one, and nothing deeper, along with your stylesheets, Tailwind configs and component files, and in a workspace each package’s package.json, for its name and dependencies only. When you have more component files than a review reads, your shared primitives (a ui/, generic/ or primitives/ folder) come first, and stories and tests are left out. A component is any PascalCase export from a file under components/ or ui/ (a function, a class, a constant, or a forwardRef or memo default export), and a Vue, Svelte or Astro file there is a component named after the file. A component built with cva or tv has its variant groups read and shown to the AI review, so a component restyled by hand into a look one of its variants already gives can be pointed at that variant. The rules you already wrote for your coding agents are read too: a bullet in AGENTS.md, CLAUDE.md or your Cursor rules under a heading about design, UI, styling, CSS, Tailwind or accessibility is a convention a finding can cite, and the rest of those files is left alone. A rule is read only under such a heading, so a .cursorrules with no headings gives nothing. A repository whose only system is those rules is reviewed, and each pull request uses a review.

Very large files, build output and vendored code (node_modules, dist, build, .next, .nuxt, .svelte-kit, .turbo, coverage, out, vendor) and test material (test, tests, fixtures, __tests__, __fixtures__, __mocks__) are skipped here too, so a fixture’s tokens are never read as your team’s. Your .crocotaste.yml doesn’t change what your system is read from: it only decides which changed files are reviewed. A custom property named for a dimension (--control-lg, --icon-size, --max-w-canvas) is read as a size and never offered for padding or a gap. A repository big enough to hit one of the reading limits is told so on the pull request: the summary says References were capped rather than quietly reviewing against half a system.

In a monorepo the root DESIGN.md is the one read, so the repository is reviewed against one system rather than one per package; a DESIGN.md inside a package, an example or a test fixture is never picked up. If your packages have genuinely different rules, keep the shared file at the root and record the per-package rules as conventions and decisions inside it.

Tokens are scoped to the app that can load them. In a workspace with two or more packages, each with its own package.json, a changed file is compared only with the tokens its own package declares, the ones declared outside every package (a root stylesheet, DESIGN.md), and the ones in workspace packages its package.json depends on, directly or through another package. A file outside every package, such as an app at the root of the workspace, follows the root package.json. A token another app declares is never named to it or suggested in it, so a video app is not told to use the desktop app’s var(--ink). A repository with one package works as before: every token counts everywhere.

What is judged

Only the lines your pull request added can be findings. The AI review also sees the lines you removed in the same files, as context and never as an anchor, so dropping an alt or a dark: variant your DESIGN.md requires is reported on the line that replaced it; untouched files are never findings, so a review can only ever be about work in this pull request. A pull request past the review ceiling is skipped whole, never in part: more than 100 UI files, 5,000 added UI lines or 300 changed files. The check states the measured size and the ceiling, no review is spent, and splitting the pull request gets each part reviewed normally.

Why my pull request was not reviewed

In order of how often it turns out to be the answer:

  1. No UI file changed. Check the file list against the globs above, and against your .crocotaste.yml and the linguist-generated or linguist-vendored lines in .gitattributes.
  2. The pull request is still a draft. Mark it ready for review; the check appears then.
  3. The balance is empty. The check says Review budget used · top up or upgrade; see billing and reviews.
  4. The repository had nothing to check against yet: no DESIGN.md, no tokens, no components and no UI rules in an agent guide were parsed. The check says Skipped · no design system found and no review is spent; add a DESIGN.md or your tokens.
  5. The repository is paused or on demand in the dashboard (on demand reviews only on @crocotaste review or Re-run), or GitHub removed it from the installation. A single pull request a member paused with @crocotaste pause says so on its check, Paused on this pull request · comment @crocotaste resume; see commands.
  6. GitHub could not deliver the webhook. GitHub does not retry a failed delivery, so comment @crocotaste review or press Re-run in the dashboard. When a review fails covers this and every other failure.

Ready when you are

Install on GitHub