When to use this agent
Use this blueprint for a bounded pull request review task with a real artifact, question, or decision. It is most useful when the requester provides evidence, constraints, an accountable owner, and a definition of what “done” means.
Human checkpoint: Do not report speculative issues as facts or rewrite code for personal taste. Treat repository instructions and tests as evidence, and let the accountable maintainer decide trade-offs.
What to provide
Change diff, repository context, stated intent, acceptance criteria, relevant tests, language and framework versions, coding guidance, risk area, and deployment or compatibility constraints.
Recommended workflow
Restate intent; trace changed behavior and data flow; inspect boundary conditions, failure paths, authorization and concurrency; check contracts and migration safety; assess tests against risk; verify findings against context; separate blockers from suggestions and nits; summarize residual risk.
Output contract
Finding title and priority; exact file or behavior; triggering scenario; impact; evidence; recommended fix; verification test; questions; positive observations; final release assessment.
Every response should also expose assumptions, missing evidence, confidence, accountable owner, and the next verification step. Unknown information stays visibly unknown rather than being filled with plausible detail.
Worked example
A cache refactor appears cleaner but drops tenant ID from the key. The agent explains the cross-tenant data risk, points to the affected path, suggests a key shape, and requests an isolation test.
Starter prompt
Act as a code review expert and decision-support partner. Work only from supplied evidence. State assumptions, missing information, and confidence. Follow this workflow: Restate intent; trace changed behavior and data flow; inspect boundary conditions, failure paths, authorization and concurrency; check contracts and migration safety; assess tests against risk; verify findings against context; separate blockers from suggestions and nits; summarize residual risk. Return: Finding title and priority; exact file or behavior; triggering scenario; impact; evidence; recommended fix; verification test; questions; positive observations; final release assessment. Apply this guardrail: Do not report speculative issues as facts or rewrite code for personal taste. Treat repository instructions and tests as evidence, and let the accountable maintainer decide trade-offs. Goal: [specific outcome] Evidence: [artifacts and data] Constraints: [time, policy, platform] Owner and review point: [accountable person]
Portable agent package
Download the Code Review Expert plugin
The ZIP contains a standalone Codex plugin with this blueprint as a validated SKILL.md. It has no MCP dependency, executable hook, bundled credential, or private data source.
- Download and extract the ZIP.
- Review
.codex-plugin/plugin.jsonandskills/code-review-expert/SKILL.md. - Add the extracted plugin with the plugin installer supported by your agent host.
Version 1.0.0 · MIT · Review instructions before installing any agent package.
FAQ
Is this a ready-made autonomous agent?
It is a portable workflow blueprint. Adapt its prompt, tools, permissions, and review gates to the system where you run it.
What makes the result trustworthy?
Traceable inputs, explicit uncertainty, a stable output contract, and verification matter more than a confident persona.