Tagged code-review

Review code logging patterns and recommend evlog adoption for entry points

Combine static analysis with model-assisted review for security and correctness

Review code for security flaws, performance problems and production reliability

Write pull request descriptions that make code changes faster to review

Review an open GitHub pull request and post inline comments on its diff

Give each task to a fresh sub-agent and review code between tasks for quality

Review GitHub pull requests from several angles with parallel subagents

Review a PR diff by severity and return findings, fixes and a merge decision

Review code in a repository with a structured workflow and findings

Review code changes from several perspectives with structured findings

Run a five-stage code review rated Blocker, Major, Minor or Nit with fixes

Review pull requests for decay risks and design smells with concrete remedies

Apply Rust naming, formatting and clippy style rules during code review

Spot Rust anti-patterns like clone-everywhere and unwrap abuse during code review

Review code for likely problems, quality issues and best-practice fixes

Review pull requests against the live base branch and judge merge readiness

Delegate coding tasks and code reviews to the local Codex CLI from your session

Run a blind dual code review with up to two scoped fix and re-judge rounds

Check code review feedback for accuracy before implementing each suggestion

Request an independent code review after each slice or before merging risky work

Review changed code for naming, stale references and needless complexity

Closeout pass that runs refactor, code review and docs before you commit

Review code for correctness, test coverage and merge readiness

Review code for OWASP risks, auth flaws, leaked secrets and bad input handling

Review code for quality, security flaws, performance and standard practices

Guide thorough code reviews with a focus on security and code quality

Review git diffs and leave inline GitHub PR comments before pushing

Review finished work against the requirements before you merge it

Review code, plans or live pages with Crit inline comments and structured feedback

Fan code reviews out to several models and merge their verdicts into one result

Review code for security issues and MX tag compliance before merging

Review MATLAB code for quality, performance and MathWorks coding standards

Review a GitHub pull request for bugs and standards and report findings

Run a pre-commit review with security scans, quality gates and auto-fixes

Check CloudBase web, mini program and function code for known pitfalls and misuse

Compatibility alias that forwards code review requests to cs-review

Run code review, QA, performance and security checks before a release ships

Run a structured code review on request, preferring Codex before other reviewers

Review code systematically for bugs, security, style and performance problems

Review pull requests for security, performance, testing and design issues

Review code for injection, XSS, auth and crypto flaws with confidence ratings

Get an independent second-opinion code review from the OpenAI Codex CLI

Apply rigorous coding standards when writing, changing or reviewing code