Menü
How to run the sanitizer to format and lint code in the bzd monorepo
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
How to write, build, test, and contribute Node.js/JavaScript/Vue code in the bzd monorepo
How to run, test, build, type-check, format, and manage Python dependencies in the bzd monorepo
Core software design principles — ALWAYS load this before planning and before writing any implementation code
How to build, test, run, and maintain Bazel targets in the bzd monorepo — always load this before invoking any ./tools/bazel command
How to read, write, and wire BDL (Bzd Description Language) files and their Bazel rules in the bzd monorepo — load this before touching any .bdl file or bdl_* Bazel rule
How to write, build, test, and contribute C++ code in the bzd monorepo
| name | bzd-sanitizer |
| description | How to run the sanitizer to format and lint code in the bzd monorepo |
| compatibility | opencode |
The sanitizer formats code and checks structure across all languages (C++, Python, Node.js, Rust, Bazel). Always run it before committing.
./tools/bazel run //:sanitizer
This is the fastest option — only checks files that have been modified. Use this during development.
If there are no staged/staged files to sanitize, it will fall back to using the latest commit.
./tools/bazel run //:sanitizer -- --all
Use this when you need to sanitize everything (e.g., before a major commit or after pulling large changes).
./tools/bazel run //:sanitizer -- --check
./tools/bazel run //:sanitizer -- --check --all
Useful for CI checks or to see what would change without actually modifying files.
# Using --all with a path
./tools/bazel run //:sanitizer -- --all cc/bzd/core
# Or just the path (shorthand)
./tools/bazel run //:sanitizer -- cc/bzd/core
This sanitizes all files under the specified directory.
Always prefer running without --all whenever possible. The sanitizer operates on changed files only and is significantly faster:
--all: ~seconds (checks git-tracked changes)--all: ~minutes (checks entire repository)To exclude a directory from sanitizer checks, place a .sanitizerignore file in that directory.
After the sanitizer modifies files, re-run the affected tests:
./tools/bazel test //path/to/affected/...