Perform a deep, scoped review of a working tree, staged diff, commit range, branch diff, pull request, focused file set, or pasted code. Use for `/code-review`, PR or diff review, and merge-safety assessment. Begin with a read-only orchestration-assessment subagent that decides whether one reviewer or multiple specialist subagents are justified by the change scope and risk. Prioritize correctness, regressions, security, privacy, contracts, data, concurrency, migrations, and tests. Persist the canonical Markdown review report and do not edit code or Git state unless the user separately requests fixes.
Consume a code-review Markdown report, PR feedback, or equivalent review comments; re-verify every finding, question, test gap, and uncovered area; formally challenge incorrect or stale review claims with arguments and evidence; and implement confirmed actions through a coding subagent. Use after code review when Codex must decide what still applies, produce a complete disposition ledger, fix proven issues, close coverage gaps, verify changes, and persist the canonical receiving-code-review resolution report. Begin with a re-review assessment subagent that decides whether multiple specialist subagents are warranted by both the change scope and review results. Preserve the user's Git index unless staging or publishing is explicitly requested.
Evidence-first runtime debugging that maximizes the probability of identifying an application bug's root cause in a single reproduction. Use for bugs, regressions, flaky or timing-sensitive failures, expensive or hard-to-repeat reproductions, and requests such as "instrument broadly", "consider every plausible cause", "capture more breakpoints", or "find the root cause in one run". Build a broad but deduplicated causal hypothesis set, map hypotheses to structured high-information probes across boundaries, branches, state transitions, asynchronous work, caches, and external calls, collect correlated NDJSON evidence with the bundled local collector, summarize large logs without loading the full file into context, prove the causal chain, apply the smallest fix, verify with before-and-after evidence, and remove temporary instrumentation.
Use and maintain the `mr` Node CLI for generic Git MR/PR branch workflows. Use when the user asks to create, preview, configure, troubleshoot, install, update, uninstall, or explain MR/PR flows with `mr`, `mrm`, `mrt`, or `mrp`; when handling branches named like `mr/target/current`, strategy flags `--merge`, `--rebase`, `--merge-target`, `--pr`, default detached mode (`--detached`, `--no-detached`, `MR_DETACHED`, `mr.detached`), detached conflict worktree placement (`MR_WORKTREE_DIR`, `mr.worktreeDir`), request providers or commands (`MR_REQUEST_PROVIDER`, `mr.requestProvider`, `MR_REQUEST_COMMAND`, `mr.requestCommand`, CNB/GitHub/GitLab), automatic update notices (`MR_NO_UPDATE_CHECK`, `NO_UPDATE_NOTIFIER`), conflict resume, `--rm-mr`, `--dry-run`, diagnostics flags, or the upstream `JUNERDD/mr` implementation behind this CLI.
Coordinate non-trivial multi-step work with delegation-first subagent scheduling. Use when work can benefit from parallel exploration, implementation, review, verification, queued independent requests, large repositories or monorepos, migrations, dirty worktrees, isolated worktrees or branches; when the user asks to maximize subagent delegation or keep running workers uninterrupted; or when auditing multi-agent orchestration. After triggering, build a dependency graph, dispatch the maximum useful set of ready non-overlapping workers allowed by tools, permissions, isolation, and integration capacity, keep healthy workers running to completion, synthesize evidence, and verify the integrated result. Handle only truly trivial or non-delegable work directly.
Opt-in Cursor SDK delegation workflow for bounded coding tasks, reviewed implementation packets, Cursor internal subagents, hierarchical workstreams, follow-up packets, live Cursor SDK monitoring, and proactive Cursor API-key authorization. Use only when the user explicitly injects or names `$delegate-to-cursor-sdk` / `delegate-to-cursor-sdk`; otherwise do not select it proactively.
Deeply pressure-test a plan or design by asking one question at a time until assumptions, tradeoffs, risks, failure modes, and scope edges are explicit. Use when the user asks to be grilled, wants a plan or design stress-tested, or needs the live conversation kept in sync with a local Markdown Q&A log.
Consume a `thermo-review` Markdown report, PR feedback derived from one, or structural quality-gate feedback involving `Blocker`, `Major`, `Minor`, `Question`, `Complete Findings Index`, `Decomposition Gaps`, recursive coverage, line-count ledgers, candidate sweep logs, `Not covered` rows, or 350-line thresholds. Use when Codex must verify every structural item against the current checkout, build a disposition and behavior-parity ledger before editing, fix, disprove, narrow, waive, or carry forward each item with evidence, avoid user-visible regressions during structural cleanup, and leave Git staging untouched unless explicitly asked to stage, commit, or publish.