gate-fix

To fix mix consistency pipeline failures blocking Elixir CI merges, repeatedly run the pipeline, identify the failing stage, and apply stage-specific mechanical remediation for formatting or credo strict offenses without altering business logic.

You can automatically resolve Elixir compilation warnings-as-errors by applying safe, mechanical fixes to unused code patterns and formatting, ensuring no business logic changes are made to silence the warnings.

A refactor plan for Phoenix credo strict or dialyzer failures is an actionable document generated when mechanical fixes are insufficient, detailing necessary code changes for human review and approval.

Gate-fix works with doctor and dialyzer stages in a fail-fast CI workflow by mapping the last executed failing stage to deterministic actions and applying targeted remediation.

You should not use automated remediation for Elixir mix consistency errors when only refactor-class issues remain, requiring the system to stop and emit STATUS: PLAN_PENDING or STATUS: BLOCKED for human intervention.

The best way to handle mix formatting and documentation failures in an Elixir project is to iteratively run mix consistency, detect the specific failed stage, and apply the corresponding safe corrective action automatically.