Is every Turborepo cache hit a correct one?
Paste or drop one Turborepo monorepo's task configuration - turbo.json, the root and workspace
package.json files, pnpm-workspace.yaml and the CI workflow that runs turbo.
Your browser reads every task, package and turbo run command and checks whether turbo accepts
the configuration and whether a cache hit restores the right thing: Turborepo 1
pipeline syntax on Turborepo 2, a missing packageManager, a task a command runs
that nothing defines, a TURBO_TOKEN written into CI, builds with no outputs or outputs that
miss .next, and deploys that a cache hit silently skips, dev servers that are not
persistent, inputs without $TURBO_DEFAULT$, CI variables strict mode hides,
loose env mode, GITHUB_SHA in globalEnv and --force in CI. Free,
before you sign in, and nothing is uploaded. Then pick a lane: the audit gives exact edits
for each finding, or the fix lane writes the whole fixed files - and the page re-checks
both.
The companies, hosts, tokens and packages in the examples are invented. The first three are audits (the first also carries a saved fix run of its edited files, one click after the audit), the last a fix run; each comes with a saved model reply, so you can see the whole page without signing in or spending a credit.
The audit rates the configuration, the task graph, the outputs and the hash inputs, confirms or dismisses every flag below, adds what rules cannot see, and gives exact before/after edits for each finding - which the page applies to your paste, re-parses and re-checks.
What this does, and what it does not
The check is a reading of the text, not turbo: nothing is installed, hashed or run. JSON files are parsed
with comments allowed and the line of every key kept, so each flag points at the line it is about; every
task definition is read with its dependsOn, outputs, inputs,
env, cache and persistent, every package with its scripts and the
framework it builds with, and every turbo command in package scripts and CI lines with its
tasks and flags. Each flag carries the catalogue id it comes from. The remote cache, the machines, the
.env and tsconfig files and the source you did not paste are not visible: which variables a
build reads, which package manager version CI installs, or whether the cache server speaks https is a
question you answer in the note, not something the page assumes. turbo run build --dry=json
and --summarize - every task's hash inputs and cache status - remain the ground truth.
The paid lanes see your paste and the page's facts. Every quote and edit they return is checked against your paste, every edit and every returned file is put back, re-parsed and re-checked, and a reply that repeats a credential from your paste is called out. A paste stays in this browser unless you run a lane. Derived from the agent skill @wshobson/turborepo-caching by Seth Hobson (wshobson/agents, MIT). Sources are listed in llms.txt.