band

Schedule a recurring prompt against a Band workspace's coding agent via a cronjob, with an optional self-deleting "stop when criteria is met" wrapper. Use when the user wants to "loop on X every 10m", "keep retrying until Y", "poll the deploy every 5 minutes", "check in every hour until tests pass", "run this prompt on a recurring interval", or otherwise asks for an iterative/repeating agent task. Wraps `band cronjobs create` so the agent re-runs the same prompt on a fixed cadence (default 10m), and optionally appends a stop-condition that makes the agent delete its own cronjob with `band cronjobs delete` when done. Caps loop lifetime at 7 days by default to match the safety horizon Claude Code's built-in `/loop` uses.

Programmatic workspace management for Band. Use when the user wants to create, list, or remove Band workspaces or projects, manage tunnels, manage cronjobs, or check settings via the Band CLI. Triggers include "create workspace", "list projects", "band workspace", "band project", "schedule a job". For sending chat messages to coding agents, see the `band-chat` skill.

Manage Band browser tabs via the CLI. Use when the user wants to create, list, navigate, inspect, or remove a browser tab inside a Band workspace. Triggers include "open browser", "navigate to URL", "browser tab", "browser pane", "remove browser tab".

Send messages to coding agents, stream their output, and manage chat panes via the Band CLI. Use when the user wants to send a chat message, watch a chat's running task, list, create, stop, remove, or label agent chat panes. Triggers include "send message to chat", "chat with agent", "watch chat", "stream chat output", "create chat pane", "list chats", "stop chat", "remove chat", "label chat", "tag chat", "submit prompt to workspace".

Manage Band terminal sessions via the CLI. Use when the user wants to create, list, send input to, read output from, attach to, or kill a terminal session inside a Band workspace. Triggers include "run command in terminal", "create terminal", "send to terminal", "terminal output", "attach terminal", "terminal pane".

Kick off work on a new feature, bug fix, or task in a fresh Band workspace. Use when the user describes a piece of work and wants an agent to start on it — "start working on X", "create a workspace and implement Y", "kick off a task for ABCD-1234", "spin up a worktree to fix

Master orchestrator that burns through a project backlog. Runs as a project-scoped cronjob on the main branch — scans GitHub issues labeled `backlog-burner`, manages one workspace per issue, dispatches implementation work via `band chats send`, and merges PRs itself (from outside the workspace) once CI is green and there are no outstanding reviewer remarks. Use when setting up automated backlog processing, orchestrating multiple agents, or supervising workspace-level work across a project.

Run Band's CI PR review locally before pushing, then auto-apply the fixes. Invokes the `review-changes` skill (the orchestrator that dispatches the coding/testing/security/performance specialist reviewers in parallel and returns sectioned findings plus a Verdict line), then applies each finding's `Fix:` with Edit/Write and verifies with lint, clippy, and tests. Use when the user says "review my branch before I push", "review and apply", "pre-flight check", "do a local PR review", "run the CI review locally", or "review my changes and fix them".

Run Band's four-specialist PR review on a branch or open PR. Gathers context (changed files, linked GitHub issue acceptance criteria, PR details, repo conventions), dispatches the coding/testing/security/performance reviewers in parallel, and returns findings organized by section plus a single overall Verdict line (`approved 👍` or `request changes 👎`). Read-only — never modifies files; the caller decides what to do with the findings (the `review-and-apply` skill applies them, the CI workflow posts them as comments). Use when the user asks for a code review, a pre-push review, or asks to vet a PR against Band conventions.

Implement a black-box integration test for a feature against the REAL application — the same binary you ship runs inside the test, external services are stubbed with Express servers on random ports (never MSW, never page.route on your own routes), and tests drive either via real HTTP (backend) or via Playwright + Page Object Model (frontend). Backend and frontend tests share the same server boot and fixtures. Use when asked to "write a test", "add integration test coverage", "add a regression test", "write a Playwright test", "test this endpoint end-to-end", or any time a new feature ships and needs the test that proves it.

Drive a Band coding-agent chat from the CLI against a local dev server for verification or smoke testing. Use when you need to exercise a chat / agent adapter end-to-end without clicking through the dashboard — e.g. verifying a new adapter in `packages/coding-agent/src/adapters/`, regression-testing after a refactor, or capturing structured agent output to assert on. Handles the dev-vs-prod port mismatch (the CLI defaults to port 3456 but `pnpm dev:web` typically lands on 3457/3458 because the production Band server is already on 3456) by pointing the CLI at the dev server via `BAND_SERVER_URL`. Triggers include "smoke-test the codex adapter", "verify the agent works end-to-end", "test the chat from the CLI", "drive a chat from the terminal".

Workspace-level implementation agent that picks up work from a GitHub issue, tracks progress via issue comments, creates PRs, handles review feedback, and merges when approved. Designed to be invoked repeatedly by the backlog-burner orchestrator or manually via band tasks. Use when an agent needs to implement a GitHub issue end-to-end in a Band workspace.

Tests the Band web application by starting the dev server, navigating pages, and capturing screenshots using agent-browser. Use when asked to test the web app, take screenshots, check how the app looks, visual test, test the UI, screenshot pages, browser test, visual regression, or verify the layout. Does NOT run unit tests, integration tests, or modify application code.