// Use when you need to load a specific published preview/nightly extension build into the agent's MCP browser by run-number, branch name, or tag. Faster than rebuilding locally when you only want to exercise an existing artifact.
Use to monitor an open PR for AI/bot review comments, evaluate them critically, push fixes for real issues, and resolve threads — capped at a sensible duration so it self-terminates. Invoke as "babysit PR
Use when an extension change needs agentic verification in a real browser — content scripts, popup UI, network calls, fonts, console errors. Spawns the agent's own Chrome via the chrome-devtools-ext MCP. Complements (does not replace) human-eye verification via `pnpm dev:browser`.
Use when about to write or modify a Playwright e2e spec under `packages/danmaku-anywhere/e2e/`. Points at the canonical doctrine and surfaces the load-bearing rules so the spec doesn't get bounced in review.
Use when evaluating review comments from AI reviewers (gemini-code-assist, copilot-pull-request-reviewer) on a PR. Default to assuming the reviewer is right; verify before declining. Includes reporting in chat and resolving threads after handling.
Use when finishing a brainstorm, writing a design spec, or producing an implementation plan in this project. Directs the output to ClickUp as a doc on the DA-XXX task instead of saving to the repo or local disk.
| name | preview-build |
| description | Use when you need to load a specific published preview/nightly extension build into the agent's MCP browser by run-number, branch name, or tag. Faster than rebuilding locally when you only want to exercise an existing artifact. |
Resolve a GitHub release published by CI (nightly or branch-preview), download its Chrome zip, expand to .tmp/, and install_extension it via the chrome-devtools-ext MCP. For active HMR development use browser-verify instead.
gh CLI authenticated against this repochrome-devtools-ext MCP (see browser-verify for install)unzip (macOS/Linux/git-bash) or Expand-Archive (PowerShell)If any are missing, stop and tell the human.
By nightly run-number (the (<BUILD>) in the title):
gh release list --limit 50 --json tagName,name \
--jq '.[] | select(.name | test("\\(<BUILD>\\)$")) | .tagName'
By branch:
gh release view preview-branch-<branch-slug> --json tagName,assets,name
Latest nightly:
gh release list --limit 5 --json tagName,name,createdAt \
--jq 'map(select(.name | startswith("Preview Build nightly-"))) | sort_by(.createdAt) | last | .tagName'
Substitute <BUILD> / <branch-slug> at the call site.
Both shells end with an unpacked/ directory under .tmp/ (gitignored).
Unix / git-bash:
TAG=<tag from step 1>
ASSET=$(gh release view "$TAG" --json assets --jq '.assets[] | select(.name | endswith("-chrome.zip")) | .name')
DEST=.tmp/preview-$TAG
mkdir -p "$DEST"
gh release download "$TAG" --pattern "$ASSET" --dir "$DEST"
unzip -q "$DEST/$ASSET" -d "$DEST/unpacked"
PowerShell (parse the JSON in PowerShell rather than passing a jq filter through the native-command boundary, which mangles quotes):
$TAG = '<tag from step 1>'
$ASSET = ((gh release view $TAG --json assets | ConvertFrom-Json).assets | Where-Object { $_.name -like '*-chrome.zip' }).name
$DEST = ".tmp/preview-$TAG"
New-Item -ItemType Directory -Force -Path $DEST | Out-Null
gh release download $TAG --pattern $ASSET --dir $DEST
Expand-Archive -Path "$DEST/$ASSET" -DestinationPath "$DEST/unpacked" -Force
install_extension(<absolute path to the unpacked dir>)
Resolve the absolute path from the current working directory (pwd / Get-Location); don't embed a host-specific prefix.
The dev API (globalThis.__da) is NOT present in these builds; nightly tags ship prod, and attachDevApi is gated by !IS_DA_PROD. Seed state via chrome.storage.set directly.
uninstall_extension(<id from list_extensions>)
Close lingering chrome-extension://<id>/... tabs first.
run_number.-chrome.zip asset.