Tool usage

Run pre-commit checks before committing Carbon language code to ensure code quality and validate formatting. This mandatory step prevents unsafe commits and maintains project standards across local development and code reviews.

Set up Carbon Language local development by installing Bazelisk for builds and tests, then configuring pre-commit checks. This provides clear, repeatable tooling guidance that reduces misconfigurations and aligns with CI conventions.

Use Bazelisk instead of Bazel directly for Carbon builds to enforce project tooling conventions. Bazelisk manages the correct Bazel version automatically, reducing unsafe tool usage and preventing version mismatches across CI and local environments.

Pre-commit checks are required for Carbon language code to enforce quality standards before changes are submitted. Mandating these checks prevents unsafe commits and ensures consistency across CI, local development, and code reviews.

Standard build tools bypass Carbon language project conventions, risking misconfigurations and unsafe tool usage. Without Bazelisk and pre-commit checks, builds and tests may fail CI validation or introduce unvalidated code into the repository.