dev-pipeline

An audited code pipeline orchestrates repository auditing, implementation planning, subagent coding, and cross-review to safely ship code changes. It requires a Codex audit, an approved plan, and a coder subagent phase before applying fixes.

The best way to plan code changes after a repository audit is to generate an explicit implementation plan detailing files, tests, and risks, then gate execution on user approval. This ensures the coding subagent follows a controlled, reviewed workflow.

Small code patches under 5 lines bypass the full cross-review workflow. The pipeline includes a safe micro-fix exception that skips the mandatory audit, plan, and cross-review phases to avoid unnecessary overhead for trivial changes.

Cross-review works by having Claude and Codex act as two independent reviewers checking the subagent implementation against the original plan. This dual-reviewer mechanism ensures code changes meet requirements before any fixes are applied.

Yes, approval gating requires you to explicitly approve or correct the generated implementation plan before the coding subagent begins. The pipeline pauses after generating the plan to ensure user control over the proposed file changes and tests.

Your code pipeline requires an audit before changes to establish a controlled starting point by summarizing key repository findings. This mandatory Codex audit prevents blind modifications by ensuring the implementation plan addresses existing codebase conditions.