Use when running Codex CLI code review for uncommitted changes, a PR branch, or a specific commit, especially for second-model review or merge-readiness closeout.
Diagnose what's overloading a hot or sluggish Mac. Checks load average against core count, ranks top CPU/memory consumers, and walks process trees to find runaway agent sessions (leftover AI coding-assistant sessions are a common cause). Use when a Mac's fans…
Use when creating, replacing, refining, or shipping a product logo, brand mark, wordmark, favicon, application icon, or identity system across a real product.
Use only when the user explicitly requests adversarial, hostile, end-to-end, or release-gate QA beyond the project's normal verification suite.
Use when a technical decision depends on current official documentation, upstream source, standards, release notes, or comparative best-practice evidence.
Use when a requested change is genuinely ambiguous about its goal, boundaries, acceptance criteria, or irreversible tradeoffs; skip when repository context supports a safe, reasonable interpretation.
Use when the user requests code review, an explicit execution workflow requires independent review, or a substantial change needs a merge-readiness assessment.
Use when the user asks to analyze, investigate, explain why something happens, or provide a grounded cross-file explanation without modifying code.