Commands

Typed as a pull request comment: @crocotaste review re-runs a review, ignore dismisses findings, and pause and resume switch a pull request off and on.

Everything Crocotaste does can be driven from the pull request, because that is where the conversation already is. There is no CLI, and the one setting, the review mode, is a menu in the dashboard.

@crocotaste review

Re-runs the review against the pull request’s current head commit. Post it as an ordinary comment on the pull request, or inside any inline review thread.

Use it after a neutral check, after topping up a balance, or whenever you want a fresh pass. Nothing already posted is repeated. A pull request’s review covers two AI reads; a command that has the AI read it a third time spends one review, and a command with nothing new to read (the same UI lines against the same design system) is free and says so. It is also how a member reviews an outside contributor’s pull request, which waits until one asks, and the only way a review starts on a repository set to on demand. It runs up to 20 times an hour per installation.

The dashboard’s Re-run button does the same thing without touching a webhook, which is the one recovery path that works even when a delivery was lost.

@crocotaste ignore <reason>

Reply to one of Crocotaste’s inline findings with this. It has to be a reply to the finding itself; a top-level comment has no finding attached, so it dismisses nothing, and Crocotaste says so once an hour on that pull request:

Nothing was dismissed: `@crocotaste ignore <reason>` works as a reply to one of the findings. To dismiss several at once, comment `@crocotaste ignore all <reason>` or `@crocotaste ignore <path> <reason>`.

Three things then happen:

  1. The finding is dismissed for this pull request: its comment is marked resolved, and the summary keeps it listed as dismissed. It will not come back here on any later push.
  2. For an AI finding, Crocotaste replies in the thread with a ready-to-paste block for your DESIGN.md’s ## Decisions section: a title, your reason and the source line already filled in.
  3. That reply carries a prompt for your coding agent to add the block to DESIGN.md. How the change lands (a branch, a pull request, its title) stays your team’s call.

The review then runs again on the same commit without spending anything, so dismissing the last open finding turns the check green; the approval follows when the model’s last read covers these lines, and never on an outside contributor’s pull request. A dismissal never posts new findings: if the per-push limit held some back, they post on your next push, in one review, not one per dismissal.

A deterministic finding (a raw value measured against your tokens) gets a shorter reply: those checks read your tokens, not your Decisions section, so a recorded decision can’t change what they flag. Make a token of any value it names that belongs in your system (a comment can name several values on one line); the checks follow your tokens from the next review on.

If the same finding was dismissed on other pull requests before, the reply says how many. A rule that keeps needing dismissal is one worth recording.

Every dismissal reply ends with an address for telling us the finding itself was wrong, so we can fix the check rather than your DESIGN.md.

No DESIGN.md yet? The reply drafts the file’s first ## Decisions section instead, and links the instructions for your coding agent. Reviews run either way (without the file they are grounded in the tokens and components parsed from your code), but a decision needs somewhere to live.

Merge the decision and it holds everywhere: on every future review, and in every agent that reads the file before writing UI. Leave it unrecorded and the same finding can resurface on a different pull request. That is on purpose: a dismissal that only lived in our database would be an invisible exception list nobody on your team could read, review or revert.

The reason is optional, but a decision without a reason is a rule nobody can argue with later.

@crocotaste ignore all <reason> and @crocotaste ignore <path> <reason>

Dismisses every open finding on the pull request, or every one whose file matches the path, in one go. Post it as an ordinary comment on the pull request, or as a review comment that is not a reply to one of Crocotaste’s findings. In a reply to a finding, @crocotaste ignore always dismisses that finding alone, and everything after ignore is the reason, so @crocotaste ignore all buttons use this shade there dismisses one finding.

@crocotaste ignore all generated by the design tool
@crocotaste ignore apps/video/** the promo is not the app

Each matching finding is dismissed for this pull request, the same way a single ignore dismisses one, and the summary keeps it listed as dismissed. Up to 50 of their comments are collapsed as resolved, and the reply says how many stayed expanded if there were more. Crocotaste posts one reply on the conversation with the count. It drafts no decision per finding; for an AI finding you want to hold everywhere, record it in your DESIGN.md’s ## Decisions section yourself, and for a raw value, make it a token.

The path is read the way .gitignore reads a line:

  • Without a slash it matches a file or folder name at any depth: *.css, *.module.css.
  • With a slash, a leading one included, it starts at the repository root and covers everything under it: apps/video/**, src/legacy/, src/app.css, /app.css.
  • * and ? stay inside a name, ** crosses folders.

The word after ignore counts as a path only when it is all, or is made of path characters and has a * with a slash or a file extension, a trailing slash, or a slash with an extension. Anything else is the reason, so @crocotaste ignore and/or the brand team stays a reason, and a single file is written **/button.tsx. One command dismisses up to 500 findings, and the same command again takes the rest; it reads up to 5,000 open findings looking for them, and the reply says when either limit was reached. It counts as one ignore against the hourly limit, however many findings it dismisses.

@crocotaste pause and @crocotaste resume

@crocotaste pause stops automatic reviews of this pull request’s pushes, for a branch mid-rework or one you will review by hand. Post it as an ordinary comment on the pull request, or inside any review thread. Each push after it gets a neutral check that costs nothing and says how to turn reviews back on:

Paused on this pull request · comment @crocotaste resume

While it is paused, @crocotaste review still reviews it once, and every ignore still works: the finding is dismissed and replied to, and a push nobody has reviewed keeps its paused check rather than being reviewed by the dismissal. @crocotaste resume turns automatic reviews back on and queues the current head the way a push would, so it spends nothing a push would not, and an outside contributor’s pull request still waits for a member’s @crocotaste review.

Crocotaste replies once to each: the reply says the pull request is paused and how to resume, or that it resumed. Sending the same one again changes nothing and gets the same reply at most once an hour. Neither counts against a rate limit, so a pause is never refused. To stop reviews on a whole repository, set its review mode to paused in the dashboard; on a repository set to on demand, nothing is reviewed on its own anyway, and a resumed pull request still waits for @crocotaste review.

Who may issue a command

Anyone who can push to the repository: its owners, and the members and collaborators with write, maintain or admin access, as GitHub reports it at the moment of the comment. A comment from anyone else (an outside contributor on a public repository, a bot) is read and ignored, so a drive-by cannot spend your reviews or dismiss a finding. Their pull requests wait for a member’s @crocotaste review and are never reviewed on their own.

Where a command is read

The command must start a line of the comment:

@crocotaste review

Lines inside fenced code blocks and quoted lines (> …) are ignored, so you can quote or explain the commands in a thread without issuing them. Case does not matter, and the first command line in a comment is the one that runs.

Commands are rate limited per installation, and the two kinds are counted apart: up to 20 times an hour for @crocotaste review and the dashboard’s Re-run together, and up to 200 ignores an hour, single or bulk, so dismissing findings never uses up your re-runs. A command over its limit is not run, and Crocotaste replies on the pull request with the time to send it again:

Rate limit reached: this installation sent 200 ignores in the last hour, so this one was not recorded. Send it again after 17:24 UTC.

It says so once per pull request and kind until that time: further commands refused before it get no second reply, and one refused after it gets a new one.

What a command cannot do

  • It cannot un-dismiss a finding. The way to bring a rule back is to remove the decision from DESIGN.md.
  • It cannot change what is reviewed. The review mode in the dashboard says when a review starts and never what it checks, and the paths a review leaves out are listed in a .crocotaste.yml in your repository; what counts as UI covers both.
  • It cannot resolve the conversation. GitHub lets only someone with write access to your code do that, and Crocotaste never asks for it: the conversation’s Resolve button stays yours.

Ready when you are

Install on GitHub