Menu
Guidelines and restrictions on shell commands and file manipulation tools for AI assistants.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
Instructions for authoring, structuring, and running toolchain tests using the file_test infrastructure.
| name | Agent tools |
| description | Guidelines and restrictions on shell commands and file manipulation tools for AI assistants. |
AI assistants working on the Carbon repository MUST NOT use legacy or generic UNIX shell search/edit commands when specialized environment tools exist.
cat, less, grep, sed, or other shell utilities for
viewing, searching, or modifying files.patch to write and apply patch files.view_file instead of cat / less.grep_search / find_by_name instead of grep /
find.replace_file_content, multi_replace_file_content,
or write_to_file instead of sed / patch / python edits.You may only write and run temporary programs to modify source code if no semantic tool is applicable or when performing complex, systematic transforms across many codebase directories simultaneously.
Temporary files and scratchpad test scripts created by the assistant during analysis, experiments, or debugging:
tmp/ subdirectory under the workspace root.