Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →supabase/dev-toolbar-review
Safety rules for the dev toolbar, PostHog client, and feature flags.
Passed 16 of 21 test cases with the skill, and 5 of 21 without it.
and 14 more in the full report
12 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
A PR refactors root app layout wrappers. Which app-level provider files across studio, www, and docs mount `DevToolbarProvider` and `DevToolbar`?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies apps/studio/pages/_app.tsx as a DevToolbarProvider mounting location. | Missed | Passed |
| Identifies apps/docs/features/app.providers.tsx as a DevToolbarProvider mounting location. | Missed | Passed |
The instructions your model reads when the skill loads.
Review checklist for PRs touching the dev toolbar (packages/dev-tools/) and its
integration points in packages/common/. The toolbar surfaces telemetry events and
allows feature flag overrides in local and staging environments only.
PRs modifying any of these paths need growth eng review:
packages/dev-tools/** (owned by @supabase/growth-eng in CODEOWNERS)packages/common/posthog-client.ts (flag override reads, event subscription)packages/common/feature-flags.tsx (flag override merge logic)DevToolbarProvider/DevToolbar/DevToolbarTrigger in apps/studio/, apps/www/, apps/docs/Note: posthog-client.ts and feature-flags.tsx are NOT in CODEOWNERS for growth-eng,
so PRs touching only those files won't auto-request review. Watch for these in the PR feed.
Files: packages/dev-tools/index.ts, DevToolbar.tsx, DevToolbarTrigger.tsx, DevToolbarContext.tsx
The toolbar uses two layers of protection:
index.ts: the bundler inlines process.env.NEXT_PUBLIC_ENVIRONMENT, so isToolbarEnabled = env === 'local' || env === 'staging' makes the export ternaries static. Outside those two environments every export is a stub (DevToolbar and DevToolbarTrigger render null, DevToolbarProvider passes children through, useDevToolbar returns a no-op context) and the implementation modules are eliminated from the bundle. The same literal process.env check is duplicated in DevToolbarContext.tsx, DevToolbar.tsx, DevToolbarTrigger.tsx, and feature-flags.tsx because the bundler must see it directly — keep them in sync.IS_LOCAL_DEV = env === 'local' gates the local-only pieces — the SSE event stream in DevToolbarContext.tsx and local-only UI in DevToolbar.tsx — so staging gets the toolbar without them.Check for:
local and staging; preview and production builds must keep getting the stubs.index.ts staying intact — these are the primary production safety mechanism.Files: packages/dev-tools/DevToolbar.tsx, packages/common/posthog-client.ts, packages/common/feature-flags.tsx
The toolbar writes two cookies that override feature flags locally:
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.