Skip to content

egregore-labs/egregore / .codex/skills/review-pr

review-pr

Unverified

Use when the user says 'review PR', 'is this PR safe to merge', or 'audit PR' — runs a CTO-level 10-point review checklist on one or more pull requests. Not creating a PR (/pr) or validating local changes (/test).

Egregore review-pr Adapter

This adapter runs the canonical Egregore workflow for review-pr. Its one maintained body is .claude/skills/review-pr/SKILL.md; read that file completely and follow it here.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

Structured UX parity

This workflow has a Claude skill with user-visible structured output. After reading .claude/skills/review-pr/SKILL.md, reproduce the same visible UX in Codex:

  • Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.
  • Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.
  • Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.
  • When the source says to output a TUI box directly, paste that box as the visible response, preferably in a text fenced block.
  • If the canonical body says the command's stdout is the card and must not be repeated, that rule assumes a host that displays command output in full; in Codex, paste the card once as the visible response in a text fenced block and do not print it a second time.
  • Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.
  1. Read .claude/skills/review-pr/SKILL.md for the workflow details.
  2. Run the referenced bin/ scripts directly from Codex.
  3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
  4. For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
  5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
  6. Never call the deprecated egregore-handoff CLI for Egregore project handoffs.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall