pr-review

原文涵盖的主题

• Step 1 — Review loop (batch local fixes; push only once per batch)
• Step 2 — Archive the OpenSpec change, then I merge (OpenSpec repos only)

Preflight: run la-doctor --plugin --require-config --require-plan-store once per session before using any la- or dr- command. If it reports the missing-config finding (the one naming /la:init), run the fast path of the la:init skill, then re-run this preflight; stop and show the user its output on anything it still reports, or on any other failure. Stage 4 of 4 of the /la:pr flow. Prerequisite: /la:pr has run in this session and established BRANCH, CHANGEID, OPENSPEC, and the full tracker issue (body + comments, if there is one), and the PR for BRANCH exists. If any of that is missing, invoke the la:pr skill instead — it rehydrates and dispatches back here. The /la:pr stopping policy applies throughout this stage. Review sources. la:process-reviews owns everything per source: which bots are on this PR (la-pr-reviewers), waiting for them, fetching, validating, and handling invalid findings. Every step below that names CodeRabbit or Sonar applies only when that bot is on the PR. Codex follows reviewers.codex: when la-config get reviewers.codex prints false there is no Codex gate; when it is on and the Codex MCP server (mcpcodexcodex) is missing, STOP and tell me — never skip it silen

这里只展示节选，请以完整原文和当前要求为准。