ptp-codex-mode

Resolves Codex reviewer mode, model, and effort settings from layered configuration.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-codex-mode-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-codex-mode
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-codex-mode
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-codex-mode-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dual-reviewer pipelines need one authoritative rule for deciding whether the Codex review phase runs, which model and reasoning effort it uses, and how the codex exec command is assembled. Without a single source of truth, every orchestrator restates the resolution and skip logic, and the copies drift apart. ## Core Features & Use Cases - Layered config resolution: Reads codex.mode (auto/required/off), codex.model, codex.reasoningEffort, and the mechanical/judgment tier keys from merged config layers with a forgiving reader posture that never crashes on typos. - Reviewer gate contract: Provides the decision table the orchestrators consult — required with missing codex stops, auto with missing codex skips with a reported line, off skips without probing PATH. - Canonical invocation rule: Pins the read-only codex exec flag-append rule (model and effort flags only when set, always before the stdin marker) plus the narrow otel.* telemetry relaxation gated on telemetry mode and recorded consent. - Use Case: A team runs /ptp:review-full on a change; this skill determines that codex.mode is auto, finds codex on PATH, and the review proceeds with the configured model and effort, or reports a non-silent skip line when Codex is absent. ## Quick Start Ask the agent to resolve the current Codex reviewer mode and decide whether the Codex phase of the next dual-reviewer step should run.

Frequently Asked Questions about ptp-codex-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control whether the Codex review phase runs?▼

Set codex.mode in any config layer to auto, required, or off. Auto runs Codex when the CLI is on PATH and skips with a reported line otherwise; required stops if Codex is missing; off always skips without probing PATH.

How do I set the Codex model and reasoning effort for reviews?▼

Set codex.model to a non-empty string and codex.reasoningEffort to minimal, low, medium, or high in layered config. Each resolves independently, and the flags are appended to codex exec only when the corresponding key is set.

What happens when codex.mode has an invalid value?▼

Invalid values are ignored, leaving whatever an earlier layer validly set, ultimately defaulting to auto. The reader never throws or stops over a missing file, parse error, or out-of-enum value.

Do the /ptp:codex-* commands respect codex.mode?▼

No. Invoking an explicit /ptp:codex-* command is itself the opt-in, so those commands always attempt Codex and stop only if the CLI is genuinely missing from PATH, even when mode is off.

Does codex.mode gate a Claude reviewer?▼

No. The gate is symmetric: the main phase always runs and only the reviewer phase is gated. When roles.main is codex, the Claude reviewer always runs with no mode check, PATH probe, or codex exec invocation.

When are otel telemetry flags added to codex exec?▼

Only when telemetry.mode resolves to on and the repository-scoped consent record records consent. Otherwise the command line is byte-identical to the plain codex exec -s read-only invocation.