Use Codex + Antigravity as static-source reviewers in parallel to review a pending diff or branch-vs-master diff, aggregate and deduplicate findings, fix must-fix and should-fix items, and review again until clean. Reviewers may inspect source and git metadata only; they never build, test, install, run, format, lint, or analyze the project. The main agent must allow each live reviewer up to 30 minutes to finish. Use for heavyweight ship-readiness review before release or merge.
End-to-end JIRA issue resolution workflow. Trigger for intents such as "resolve JIRA XXXX-nn", "fix XXXX-nn", "handle XXXX-nn", or a jira.ismisv.com/browse/ URL. It runs the full loop of finding the DAG root, producing and reviewing a high-level plan, attaching the plan, coding and testing, reviewing code, committing, and writing back to JIRA. One run handles only one issue. If a story has no subtasks, split it first and implement only the first subtask; if all subtasks of a parent are complete, use the parent closeout shortcut.
Before implementation, send the current task's high-level plan to Codex + Antigravity in parallel for review, aggregate feedback, revise the plan, and review again until there are no new issues. Strictly limit both plan authoring and review to technology selection, high-level architecture, business direction and flow, and basic business logic; exclude implementation details and code expression. Use when the user says "review my plan", "review the plan before coding", "run a dual review on the plan first", or "check whether this approach is okay". Reviewers only review; they do not edit files.
Windows-only. Drive WinDbg's command-line frontend `cdb.exe` non-interactively to diagnose crashes, startup failures, hangs, and unexplained behavior in the current development build. Assumes source tree + matching PDBs are available. Use when the user asks to "debug the crash", "run under cdb", "get a stack trace", "why does it crash on startup", "analyze the .dmp", or when reading source alone did not reveal the cause. Do NOT use for post-mortem symbol-less production dumps, remote kernel debugging, or as a general-purpose REPL — the workflow is scripted `-c "...;q"` batches.
Windows-only CMake wrappers for the GarmentStyleMatch project — build, clean, and reconfigure the `cmake-msvc-build/` tree via login-shell wrappers (`cmake-build`, `cmake-clean`, `cmake-reconfigure`). Use whenever the user asks to compile / build / rebuild the project, wipe the build directory, or reconfigure after editing `CMakeLists.txt`. Do NOT invoke `cmake` / `cmake --build` / `ninja` directly — always go through these wrappers.
Invoke the Antigravity CLI (agy-wrapper) for high-level plan reviews, requirement clarification, task planning, technical consultation, or architecture review of a formed idea. Use when the user wants to "ask antigravity/agy", "have antigravity review the plan", "have agy look at my design/idea/architecture", or "ask another large model for ideas". This is not for line-level code correctness review or multi-reviewer ship-readiness workflows; when the user has already decided and only implementation remains, do not consult it, just write the code.
Use Codex CLI to perform a single structured code review of the current branch's pending diff or branch-vs-master diff. Output five issue categories (correctness / edge cases / security / compatibility / coding standards) and classify them as must-fix / should-fix / nit. Use when the user says "review the current changes", "audit this", "go over the pending changes for issues", or "scan the diff". This is a single review, not a fix loop. Optional focus instructions (such as "only look at SQL", "focus on error handling", or "ignore test files") are passed through via arguments.
Invoke Codex CLI (`codex exec -s read-only`) for deep technical consultation on specific code, edge cases, and difficult bugs: line-level code correctness review, algorithm optimization, complex logic analysis, and issue localization in complex codebases. Use when the user wants to "ask codex", "have codex look at this snippet", "have codex review this function", or "ask codex about this panic/edge case". This is not for architecture or high-level direction review; do not consult it for one-line questions you can answer yourself with 10 seconds of rg; when the user has already decided and only implementation remains, do not consult it either, just implement.