[enhancement](agent) Add more agent behavior calibration instructions (#63395)

1. clarify correct pod array usage
2. clang-format version specific

Author: zclllyybb

.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)

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 && B)` and instead use `if (A) { DORIS_CHECK(B); ... }`. In short, the principle is: upon discovering errors or unexpected situations, report errors or crash—never allow the process to continue.
 
+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.