Run an adversarial two-stage review loop — first a "hate review" subagent (opus by default, fable on request) that tears the changes apart until it signs off, then an OpenAI Codex pass until it signs off too. Use when the user asks to "hate review until it passes", "run the hate reviewer cycle", "hate then codex", or otherwise wants a hostile review gauntlet before merging. Trigger on phrases like "hate reviewer cycle", "hate review loop", "beat this up then codex it".
Review this pull request and pretend you're a senior dev doing a code review and you HATE this implementation.
Commit only your own changes by staging individual hunks via patch, never `git add .` or `git add -A`. Use whenever you are about to stage or commit in a repository that may contain changes from other agents, parallel sessions, or the user working concurrently — which is the default assumption.
Rewrite a feature branch into a clean, reviewable commit stack without changing the final file contents. Use when asked to prepare a PR by resetting existing commits and recomposing the same net changes into small, sequential commits that are easy to review one commit at a time.
Request a code review from Claude Code, implement or evaluate the feedback, and iterate until the review converges. Use when the user asks for a "Claude review", wants feedback from Claude Code, asks for a second opinion from Claude, or wants an iterative review loop between Codex and Claude on the same set of changes.
Request a code review from OpenAI Codex CLI and iterate on the feedback until both agents agree the code is good. Use this skill when the user asks for a "codex review", wants a second opinion from Codex, wants to get feedback on their changes from another AI agent, or wants an iterative review loop. Trigger on phrases like "get a review from codex", "ask codex to review", "codex review", "second opinion", "review from codex", or "have codex look at this".
Use Atlassian CLI `acli` with Jira Cloud to inspect, search, create, edit, assign, comment on, transition, and link Jira work items, and to resolve or run Jira filters by name or ID. Use when the user wants Jira issue operations performed from the terminal instead of the browser, especially for reading issue details, searching with JQL, posting or updating comments, changing status or assignee, editing summaries or descriptions, creating new work items, or running saved filters.