coding-assistant

Classify code changes as destructive or non-destructive to enforce approval gating and document specific requirements for release governance. This risk classification ensures destructive modifications are properly gated before execution and review.

A coordinated code review sequence orchestrates plan-review, source-review, and result-review steps for implementation changes. It leverages Codex for implementation tasks and Claude for independent reviews with defined fallbacks.

Generate a verification report for schema and API configuration updates by requiring explicit verification commands and capturing evidence. The final report separates verified facts from assumptions and highlights residual risks.

Yes, you can use Claude for independent code review while Codex handles implementation. The workflow applies Claude review sequences across plan, source, and result phases, including defined fallback handling if a review step fails.

Automated risk classification for developer-document changes requires explicit verification commands and may still leave residual risks. Limitations include the need to separate verified facts from assumptions and manage approval gating manually for destructive updates.

You need approval gating for configuration changes when they are classified as destructive. The classification process documents specific approval requirements and enforces gating to ensure risk-aware execution before any review sequence proceeds.