A code-review workflow that examines code for correctness, security, quality, and ease of maintenance, then rates its findings by severity. It ends with a verdict on whether the change is ready to merge.

Use it to review a code change, pull request, or major feature and receive severity-rated findings plus a merge-readiness decision.

It gives developers a consistent way to find important problems before merging or after a major feature is built. Independent review lanes can expose issues that one pass might miss.

code-review — Skill for Claude Code and Codex by mrzhangguoguo

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add mrzhangguoguo/oh-my-workbuddy --skill code-review

Clone the repo

git clone --depth 1 https://github.com/mrzhangguoguo/oh-my-workbuddy

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/code-review/github.svg)](https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/code-review)

Your own site

<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/code-review"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/code-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/code-review"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,721 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.01721
Opus 5	$0.00014	$0.00860
Sonnet 5	$0.00005	$0.00344
Haiku 4.5	$0.00003	$0.00172

Measured 10d ago against content hash 8f04d77fcbb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/code-review/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ported from oh-my-codex code-review. OMX runtime conventions ($macro invocation, omx CLI, .omx/ state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list, .workbuddy/memory).

Code Review Skill

Conduct a thorough code review for quality, security, and maintainability with severity-rated feedback.

When to Use

User requests "review this code", "code review".
Before merging a pull request.
After implementing a major feature.
User wants a quality assessment.

Behavior

Default to outcome-first reporting: state the target result, evidence, validation status, and stop condition before adding process detail.
If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the review is grounded; stop once enough evidence exists.
Continue through clear, low-risk, reversible next steps automatically; ask the user only when the next step is materially branching, destructive, credentialed, external-production, or preference-dependent.

Workflow — Two Parallel Lanes

Delegate to two independent agents via the Agent tool, run in parallel, for a two-lane review:

Identify Changes
- Run git diff to find changed files.
- Determine scope of review (specific files or entire PR).
Launch Parallel Review Lanes (use the Agent tool, two calls in one message)
- Code-reviewer lane — owns spec compliance, security, code quality, performance, and maintainability findings. Prompt it to act as a senior code reviewer.
- Architect lane — owns the devil's-advocate / design-tradeoff perspective. Prompt it to act as a skeptical architect.
- Both lanes run on a clean context with explicit scope and artifacts, and produce distinct outputs before final synthesis.
- If either lane cannot be launched or does not return evidence, report independent review unavailable; do not substitute your own authoring lane, and do not approve or mark the review merge-ready.

Read the full file on GitHub · 178 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 178 lines · 27 tokens per session scan A 8f04d77fcbb8

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,721 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review agent-skills oh-my-codex review skills workbuddy

code-review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Code Review Skill

When to Use

Behavior

Workflow — Two Parallel Lanes

What this file has done since we first saw it

Other skills, from other repositories

Security Audit Checklist

PR Standards

Security Checklist

Agent Instruction Drift Check

code-review-self

code-review