Run a safe Grok Build code review of a branch or explicitly requested local changes. Use when an external Grok review is requested for correctness, architecture, maintainability, regressions, or missing tests; the workflow invokes Grok's native /review skill, preserves durable artifacts, and never edits or publishes changes.
Run Fable, Grok, and Thermo-Nuclear code reviews concurrently against one validated, immutable Git scope, while preserving separate outputs and reporting partial failures. Use when the user explicitly asks for a parallel, three-reviewer, multi-model, or strongest available code review of a PR, branch, commit range, or comparison with main.
Use zmx for durable, long-running processes that must persist beyond the current agent session, such as an app server the user will test later.
Fetch CI build results and diagnose failures. Auto-detects provider from project files or URLs. Supports GitHub Actions, Buildkite, and CircleCI.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a written implementation plan to execute
Use when you have a spec or requirements for a multi-step task, before touching code
Write and review Ruby/Rails code in Mike's personal style — parens, conditional shape, raising finders, operations and PORO shape. Use whenever writing, refactoring, or reviewing Ruby, or when the user asks for Mike's Ruby style.