Skip to content

cross-provider review harness: one command from branch to verdict #24

Description

@jorisjonkers-dev-agents

The mandatory cross-provider review pattern (Claude implements → codex reviews; codex implements → Claude reviews) has proven its value repeatedly — in the suppression-removal wave alone the codex reviewer caught a deleted-import compile breaker, rejected an unjustified retained suppression with a concrete split sketch, and five line-length violations that local tooling could not check; Claude reviewers earlier verified lock-namespace byte-equivalence and websocket lifecycle ordering on codex branches.

Today each review is a hand-written prompt naming the worktree, the diff command, the review dimensions, the repo's lint thresholds and the verdict format. A council review --branch <worktree> --implementer <provider> command should: pick the opposite provider automatically, generate the review brief from a dimension template (behavior preservation, suppression/lint honesty, import-resolution-as-compile-substitute when local builds are blocked, test substance) plus repo lint configs, enforce the APPROVE/BLOCK + numbered-findings output contract, and store verdicts in the run directory for the orchestrator's merge gate.

The review-dimension template and verdict contract from this program are reusable as-is.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions