Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use correctness as the default lens. For large, risky, or requirement-heavy changes, add the standards and specification lenses in references/review-lenses.md. Keep each finding tied to its source; documented rules and acceptance criteria outrank personal preference.
Each finding must include:
Do not report style preferences, theoretical risks without a reachable path, or issues outside the change unless the diff materially exposes them.
Read references/review-checklist.md when the change touches APIs, data, authorization, concurrency, infrastructure, or tests.
If there are no actionable findings, say so directly and name residual unverified areas. Keep the summary shorter than the findings.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.
The English summary is being prepared. Showing the original description.
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.
The English summary is being prepared. Showing the original description.
Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.
The English summary is being prepared. Showing the original description.
Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.
The English summary is being prepared. Showing the original description.
Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.
The English summary is being prepared. Showing the original description.
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.
The English summary is being prepared. Showing the original description.