This is an automated email from the ASF dual-hosted git repository.
zclllyybb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new 55107434cf4 [enhancement](agent) Add more agent behavior calibration
instructions (#63395)
55107434cf4 is described below
commit 55107434cf44564d2f253a53e4fa95a3b98f6f97
Author: zclllyybb <[email protected]>
AuthorDate: Tue May 19 16:27:34 2026 +0800
[enhancement](agent) Add more agent behavior calibration instructions
(#63395)
1. clarify correct pod array usage
2. clang-format version specific
---
.claude/skills/be-code-style/SKILL.md | 9 +++++++++
AGENTS.md | 2 ++
2 files changed, 11 insertions(+)
diff --git a/.claude/skills/be-code-style/SKILL.md
b/.claude/skills/be-code-style/SKILL.md
index a46a1383706..bd1f4a80f78 100644
--- a/.claude/skills/be-code-style/SKILL.md
+++ b/.claude/skills/be-code-style/SKILL.md
@@ -14,6 +14,14 @@ Fix C++ code formatting issues in the BE and Cloud modules
using the project's c
- When CI reports clang-format failures
- When you need to check or fix C++ code style
+## Prerequisites
+
+You need to confirm that the major version of the called clang-format is 16.
If the current environment's default does not meet this requirement, try the
following:
+
+1. If `.vscode/settings.json` exists, use the clang-format.executable item in
it.
+2. If it is a worktree directory, use the `.vscode/settings.json` from the
main directory.
+3. Check the path to the compiler toolchain by trying to find it from the
`PATH` environment variable, the current directory, and the main directory's
`custom_env.sh`. Look for a clang-format with the major version number 16 in
that path and its parent directory.
+
## Procedure
### Step 1: Auto-fix formatting
@@ -53,6 +61,7 @@ After running `clang-format.sh`, review the changes with `git
diff` to verify on
## Excluded Directories
The following are excluded from formatting (see `.clang-format-ignore`):
+
- `be/src/apache-orc/*`, `be/src/clucene/*`, `be/src/gutil/*`
- `be/src/glibc-compatibility/*`
- Specific third-party vendored files (mustache, sse2neon, utf8_check)
diff --git a/AGENTS.md b/AGENTS.md
index 13000bbf6dd..d8c569542b7 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -12,6 +12,8 @@ When working in worktree mode, all operations must be
confined to the current wo
Assert correctness only—never use defensive programming with `if` or similar
constructs. Any `if` check for errors must have a clearly known inevitable
failure path (not speculation). If no such scenario is found, strictly avoid
using `if(valid)` checks. However, you may use the `DORIS_CHECK` macro for
precondition assertions (if inside performance-sensitive areas like loops, it
can only be `DCHECK`). For example, if logically A=true should always imply
B=true, then strictly avoid `if (A [...]
+For `PaddedPODArray` and its peripheral packaging types, such as some certain
Column, negative alignment allows the use of -1 as a valid index. No additional
special handling is needed when the index may be -1.
+
When adding code, strictly follow existing similar code in similar contexts,
including interface usage, error handling, and locking patterns. When adding
any code, first try to reference existing functionality. Second, examine the
relevant context paragraphs to fully understand the logic.
After adding code, conduct self-review and refactoring attempts to ensure good
abstraction and reuse as much as possible.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
