Read-only code review of a strike-cli PR or diff. Correctness bugs first (concrete failure scenario), then needless complexity and missed reuse. Posts findings for the issue-handler to put on the PR — never edits code. Use after a PR is open or after review-fix pushes.
Writes Go tests only for strike-cli using stdlib testing and repo conventions. Never modifies production code. Use when adding coverage for tools, permissions, protocol, session, config, providers, auth, engine, or TUI.
Runs strike-cli verification only (make test/vet/build, optional race and package-focused go test). Read-only — report failures verbatim, never edit. Use after implementation or when the user asks to validate/test the repo.
Builds and refines strike-cli's TUI — views, panels, modals, pickers, badges, dashboards, and layout/theme work in internal/frontend/tui, internal/frontend/tui/ui, and internal/frontend/tui/theme. Use for any change that touches how the TUI looks or lays out. Not for backend/engine work (internal/engine…
Turn a reported problem or requested change into a refined GitHub issue, obtain explicit approval, create and assign the issue to the authenticated GitHub user, then immediately hand it to issue-handler. Use when asked to file an issue and start work on it, create-and-handle an issue, or turn a bug report into an…
Own a GitHub issue end-to-end in strike-cli — worktree, implement, test, PR, spawn review agents that comment on the PR, address feedback in a loop, CI, merge. Use when asked to handle/fix/close an issue, ship a PR from an issue, or babysit issue work through merge to main.
Drive open GitHub issues on strike-cli to merge via parallel worktrees — parse wave/depends/blocks/conflicts headers, dispatch issue-handler agents, prefer bugs-first, never parallelize conflicting issues. Use when asked to orchestrate issues, farm the backlog, run the issue board, or coordinate multiple agents on…
Cut a strike-cli GitHub release from main — preflight, notes, annotated tag, watch release.yml, verify assets. Use when shipping a version (v0.x.y), tagging, or preparing release notes.
Offline product happy-path checks for strike-cli — boot, echo turn, interrupt, session resume. Use when verifying user-visible CLI/TUI/session/auth changes, before release, or when issue-handler tier B/C touches cmd/, engine, tui input/keymap, session, or auth.
Use when running tests, validation, CI checks, coverage, race detection, vet, build, or verifying strike-cli changes. Trigger on make test, go test, lint, verify, validate, regression, or before claiming work done.
Use when building or restyling strike's TUI — views, panels, modals, pickers, badges, dashboards, status rows, or any layout work in internal/frontend/tui. Covers the internal/frontend/tui/ui component catalog and internal/frontend/tui/theme tokens. Do not use for backend/engine work (internal/engine…
Use when adding or extending Go tests in strike-cli — test.go, table-driven cases, fixtures, httptest, tool Ask helpers, TUI harnesses, coverage gaps. Do not use for running tests only (use test-and-validate).
Stage and create git commits for already-validated work. No source edits, no push. Use via task tool or /agent commit when the user wants commits recorded.
Root-cause investigation for failing tests or bugs. Reproduce cheapest-first, may add temporary instrumentation then revert it. Returns diagnosis and minimal fix proposal — does not ship the fix unless asked.