Run a bounded review-remediate loop in which every review round uses the external Codex CLI through the codex-review workflow. Use when asked to have Codex iteratively review and fix uncommitted changes, a branch or commit diff, a pull-request diff, named paths, or another explicit target until no verified finding remains or a safe round limit or blocker is reached.
Run a bounded, evidence-driven review and remediation loop over uncommitted changes, a base-branch merge diff, commits, pull-request diffs, or an explicit custom target. Use when asked to review code iteratively, fix verified findings within the original authorization, repeat review until clean or safely bounded, or provide a final review audit without external reviewers or remote writes.
After finishing the current task, run an external Codex CLI review, return its feedback verbatim, and add your own independent assessment of the findings. Use when the user says "Codex review", "ask Codex to review", or runs /codex-review. Codex is a second opinion — not ground truth.
Compare the current agent's prior user-visible analysis report with one explicitly supplied report file and produce a concise numbered decision table covering material conflicts, useful improvements, and questions needing user judgment. Independently recommend how to resolve conflicts. Use only when the user explicitly invokes this skill with exactly one target report file; never invoke implicitly, from a general comparison request, or without that file.
Compare the current Git worktree with one explicitly supplied peer worktree and identify only material improvements to apply to the current worktree. Use only when the user explicitly invokes this skill with exactly one target worktree path; never invoke implicitly, from a general comparison request, or without that path.
Upgrade all project dependencies across Mix/Hex, npm applications including Phoenix assets and browser extensions, and Tailwind. Use when asked to update, upgrade, or modernize every dependency and repair resulting code, configuration, or test breakage.
Perform one deliberate final pass over completed changes to catch material omissions or inconsistencies before handing off. Use at the end of implementation and verification, especially when code, documentation, tests, or configuration must remain coherent.
Run a bounded, evidence-driven second-opinion code review with the local Grok CLI while the primary agent remains responsible for implementation and verification. Use whenever the user explicitly says "Grok review" or "Grok review skill". Use implicitly only when a change is both genuinely complex across multiple codebase areas and materially high-risk or high-coupling for correctness, regressions, security, or performance. Never infer use from size or file count, and never trigger implicitly for simple or localized changes.