菜单
Review code changes for correctness, security, test coverage, and documentation impact. Use when reviewing a diff, branch, or pull request.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
사용자의 막연한 아이디어를 한 질문씩 인터뷰해서 실행 가능한 MVP 스펙으로 만든다
Socratic deep interview with mathematical ambiguity gating before explicit execution approval
Consensus planning entrypoint that auto-gates vague team/ultragoal requests before execution
Multi-worker GJC tmux team orchestration
Create and execute durable repo-native multi-goal plans over GJC goal mode artifacts.
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real ~/.codex. The first-party method drives the real `codex app-server` against an isolated CODEX_HOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by asserting hook/started + hook/completed notifications. Also: isolated install verification, per-component hook probes, a tmux TUI smoke, and runtime log observation (RUST_LOG / logs SQLite / /debug-config). Ships tested helper scripts each with a --self-test. Use whenever someone changes anything under packages/omo-codex or wants to QA, smoke-test, verify, or debug the Codex plugin, its hooks/components, the installer/config.toml, the app-server flow, or the Codex TUI. Triggers: codex qa, qa codex, codex-qa, test codex plugin, verify codex hook, codex app-server, lazycodex qa, isolated CODEX_HOME, prove codex hook fired, codex tui test.
| name | pr-review |
| description | Review code changes for correctness, security, test coverage, and documentation impact. Use when reviewing a diff, branch, or pull request. |
Review in this order. Skip style nits.
docs/api-contract.md or docs/architecture.md need updates?Output format:
For each Suggested fix, include a file path and line range. Do not propose broad rewrites; propose the smallest change that resolves the issue.