Agent skill
peer-review
Run an independent peer review via codex. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "peer review my spec", "peer review my prompt plan", "get a second opinion", or "independent review".
Install this agent skill to your Project
npx add-skill https://github.com/tobihagemann/turbo/tree/main/skills/peer-review
SKILL.md
Peer Review
Independent peer review via codex. Runs /codex-exec in read-only mode with a review prompt that was passed in or derived from context.
Step 1: Identify the Review Prompt
Determine the review prompt:
- If a review prompt was passed in (in the Agent task context), use it as-is
- If no prompt was provided (standalone invocation), determine what to review from conversation context and build a prompt using
/codex-execXML tags (<task>,<structured_output_contract>, and optionally<dig_deeper_nudge>)
When building a standalone prompt, use P0-P3 priorities: P0 (fundamentally flawed), P1 (significant gap), P2 (moderate issue), P3 (minor improvement). Example:
<task>
Review the following for issues that would cause incorrect behavior or get an implementer stuck.
</task>
<structured_output_contract>
For each issue: (1) problem, (2) location, (3) impact, (4) suggested fix, (5) priority P0-P3.
If no issues, state that it looks sound.
</structured_output_contract>
Step 2: Run /codex-exec Skill
Run the /codex-exec skill in read-only mode with the review prompt.
When the prompt covers multiple review dimensions (e.g., correctness, security, quality, API usage), wrap the task list with parallel fan-out instructions so codex delegates each dimension to a separate sub-agent. Add to the prompt:
Delegate each review dimension to a separate sub-agent using spawn_agent so they run in parallel. Wait for all agents to complete, then synthesize their findings into a unified report.
See /codex-exec references/parallel-execution.md for details on codex parallel execution.
Step 3: Output Findings
Output the codex findings.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
review-api-usage
Check API, library, and framework usage in code against official documentation and installed skill knowledge. Flags deprecated APIs, incorrect method signatures, wrong parameter types, version-incompatible patterns, and best-practice violations. Use when the user asks to "review API usage", "check API usage", "verify against docs", "check library usage", "validate API calls", "check against documentation", or "check for deprecated APIs".
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR feedback", "handle review comments", "address review feedback", "respond to PR comments", "answer review questions", or "address code review".
consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", "brainstorm with codex", "discuss with codex", or "chat with codex".
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev infrastructure", or "tooling audit".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
Didn't find tool you were looking for?