consistency

Run precommit checks for Elixir by executing the `mix consistency` alias to verify linting, formatting, and documentation rules, optionally auto-fixing actionable issues before changes are accepted.

Preventing code quality drift in an Elixir Phoenix repository requires running a precommit consistency workflow that enforces formatting, linting, and documentation standards before changes are accepted.

Yes, you can automatically fix formatting and linting issues when running `mix consistency` if the configured workflow supports auto-fixing pending style and quality problems.

Yes, the `mix consistency` workflow verifies documentation expectations alongside linting and formatting to guard against regressions and ensure the repository aligns with established engineering standards.

Running Elixir precommit quality checks before opening a pull request catches and fixes style problems early, allowing reviewers to focus on actual feature work rather than formatting or linting drift.

Execute multi-stage commits after passing Elixir consistency checks by running `mix consistency`, verifying clean quality results, and then applying conventional multi-stage commits for the resolved changes.