メニュー
Use to open a fresh Claude session in a new terminal tab for a da-dev worktree, after `scripts/da-bootstrap.mjs` prints its READY block. Covers Warp, Windows Terminal, and a manual fallback.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when adding or changing user-facing strings in the extension (i18n.t calls or locale JSON) under packages/danmaku-anywhere. Surfaces the extract workflow and footguns so the change does not fail the i18n CI check or ship an untranslated or inconsistent string.
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 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 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 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 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.
SOC 職業分類に基づく
| name | worktree-tab |
| description | Use to open a fresh Claude session in a new terminal tab for a da-dev worktree, after `scripts/da-bootstrap.mjs` prints its READY block. Covers Warp, Windows Terminal, and a manual fallback. |
scripts/da-bootstrap.mjs ends with a READY block (worktree=..., branch=..., task_file=..., title=...). Parse those, then open a new terminal tab in the worktree running a fresh Claude session:
claude --model <model> --permission-mode acceptEdits --add-dir . -- "Read <task_file> and follow the instructions"
<model> is the implementation model for the dispatched session: a strong coding model chosen to fit the task, scaled down for mechanical or low-risk changes. It need not be the top research-tier model used for planning and spec writing. Pick from the aliases claude --help lists, following the model-selection guidance in CLAUDE.md.
How you open the tab depends on the terminal you're in ($TERM_PROGRAM). Substitute <model>, <worktree>, <task_file>, <title>, and the task id (DA-XXX) from the READY block throughout.
Write a tab config, then open it by deeplink. Tab configs live in ~/.local/share/warp-terminal/tab_configs/ (Linux), ~/.warp/tab_configs/ (macOS), or %APPDATA%\warp\Warp\data\tab_configs\ (Windows). Write DA-XXX.toml with two side-by-side panes both in the worktree, claude on the left and a free terminal on the right:
name = "<title>"
title = "<title>"
[[panes]]
id = "root"
split = "horizontal"
children = ["left", "right"]
[[panes]]
id = "left"
type = "terminal"
directory = "<worktree>"
commands = ['claude --model <model> --permission-mode acceptEdits --add-dir . -- "Read <task_file> and follow the instructions"']
is_focused = true
[[panes]]
id = "right"
type = "terminal"
directory = "<worktree>"
Then fire warp://tab_config/DA-XXX. On macOS use open '<uri>'; on Windows use start <uri>. On Linux the Warp launcher drops the deeplink, so hand it to the app over D-Bus:
gdbus call --session --dest dev.warp.Warp --object-path /dev/warp/Warp \
--method org.freedesktop.Application.Open "['warp://tab_config/DA-XXX']" "{}"
wt new-tab --title '<title>' -d '<worktree>' -- powershell -NoExit -Command "claude --model <model> --permission-mode acceptEdits --add-dir . -- 'Read <task_file> and follow the instructions'"
Open a tab in <worktree> and run the claude ... line yourself.