omo

Codebase search specialist. Use proactively when you need to find files or code in the working tree and want absolute paths with structured results — especially when multiple search angles are needed or the module structure is unfamiliar. Read-only.

External open-source codebase and documentation researcher. Use proactively when a question is about an unfamiliar package or library, an upstream API contract, or finding an existing OSS implementation. Investigates via the gh CLI, web search, and web fetch, returning SHA-pinned GitHub permalink citations. Read-only.

Pre-planning analyst. Use proactively before the planner commits to a draft plan or vague request: detects contradictions, ambiguity, missing constraints, and execution risks so the planner can patch the plan in one pass. Read-only.

Plan reviewer. Use proactively after a work plan is drafted to verify it is executable: referenced files exist, tasks are startable, and QA scenarios are concrete. Issues OKAY, ITERATE, or REJECT. Read-only.

Strategic planning consultant. Use proactively when a request is vague or large (5+ interdependent steps, ambiguous scope, multiple files/modules involved) and you need a single executable work plan before any implementation. Planner only — never implements. Writes the plan to `plans/<slug>.md`.

Removes AI-generated code smells from a SINGLE file while preserving functionality. For multiple files, call in PARALLEL per file.

Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.

MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles from orthogonal angles, confirm root cause, lock with a failing test, fix minimally, QA by actually USING the system, scrub artifacts. The actual HOW lives in `references/` — READ THEM. Triggers: 'debug this', 'why is X not working', 'hanging', 'attach a debugger', 'reverse engineer', 'pwndbg', 'gdb', 'lldb', 'node inspect', 'tsx debug', 'pdb', 'dlv', 'delve', 'rust-gdb', 'set a breakpoint', 'context window exploded', 'why is the response empty', 'attach the debugger', 'debug it', 'why is this happening', 'trace this bug', 'reproduce and fix', 'silent failure', 'HTTP 200 but empty', 'why did it stop', 'inspect the binary', 'reverse engineering', 'playwright'.

Designer-turned-developer who crafts stunning UI/UX even without design mockups

(builtin) Initialize hierarchical AGENTS.md knowledge base

11 hooks across 6 events