Menu
Instructions for code formatting and style guidelines in the Carbon toolchain.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Instructions for registering, mapping, constant evaluating, and lowering builtin functions in the Carbon toolchain.
Instructions for declaring, formatting, emitting, testing, and styling diagnostic messages (errors, warnings, notes) in the Carbon toolchain.
Guidelines and restrictions on shell commands and file manipulation tools for AI assistants.
Instructions that **MUST** be followed when using Bazel or Bazelisk to build, test, and debug in the Carbon repository.
Instructions for using Jujutsu (jj) for version control in the Carbon repository.
Instructions for running prek, the Carbon pre-submit/style/lint checker, that *MUST* be run before submitting an change.
| name | Code style |
| description | Instructions for code formatting and style guidelines in the Carbon toolchain. |
third_party/ should have a
license following
CONTRIBUTING license instructions.pre-commit run buildifier --files <file.bzl> to format
Bazel files.pre-commit run clang-format --files <file.cpp> to format C++
files.format command doesn't work well right now.
Instead, try to format Carbon code based on other Carbon files and the C++
style.pre-commit run prettier --files <file.md> to format
markdown files.pre-commit run black --files <file.py> to format Python
files.pre-commit run flake8 --files <file.py> to check Python style.