メニュー
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| description | Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions. |
| name | review-agent |
Inspect the requested target directly and return every finding that the author would likely fix. Do not modify files, create commits, push branches, post review comments, or delegate the review to another agent.
AGENTS.md instructions.For a base-branch review, compare the changes that would actually merge rather than diffing
directly against the branch tip. Resolve the comparison ref to the branch's upstream when that
upstream exists and is ahead of the local branch; otherwise use the local branch. Run
git merge-base HEAD <comparison-ref>, then inspect git diff <merge-base-sha>. If the local
branch cannot be resolved, try its configured upstream explicitly before reporting that the target
is unavailable.
Flag an issue only when all of these are true:
Do not flag speculative concerns, pre-existing problems, intentional behavior changes, or style nits that do not obscure the code.
Present findings first, ordered by severity. Use one entry per issue in this form:
[P1] Imperative finding title — path/to/file.rs:line
Follow the title with one short paragraph explaining the affected scenario and why the behavior is wrong. Keep the cited range as small as possible and make sure it overlaps the reviewed diff.
Use these priorities:
P0: universal release blocker or critical failure.P1: urgent defect that should be fixed next.P2: ordinary defect that should be fixed.P3: low-impact issue that is still worth fixing.If there are no qualifying findings, say No findings. Do not invent a finding to fill the result.
After the findings, add a brief overall assessment and mention any material test gaps or residual
risks.
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.