This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 0d2bcf868fe Enhance Claude.md with CODE_OF_CONDUCT.md integration and
simplification (#36932)
0d2bcf868fe is described below
commit 0d2bcf868fe3a51c6dba267bc3921db54a5f85f3
Author: Liang Zhang <[email protected]>
AuthorDate: Fri Oct 24 00:31:16 2025 +0800
Enhance Claude.md with CODE_OF_CONDUCT.md integration and simplification
(#36932)
* Enhance Claude.md with CODE_OF_CONDUCT.md integration and simplification
- Add specific CODE_OF_CONDUCT.md mappings instead of generic reference
- Include clean code principles, naming conventions, and AIR testing
principle
- Integrate CODE_OF_CONDUCT.md test coverage requirements with Quality
Assurance standards
- Add AIR (Automatic, Independent, Repeatable) and BCDE (Border, Correct,
Design, Error) testing principles
- Simplify redundant descriptions while maintaining comprehensive guidance
- Add precise assertion naming conventions (actualXXX, expectedXXX)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
* Update CLAUDE.md
---------
Co-authored-by: Claude <[email protected]>
---
CLAUDE.md | 62 ++++++++++++++------------------------------------------------
1 file changed, 14 insertions(+), 48 deletions(-)
diff --git a/CLAUDE.md b/CLAUDE.md
index 98cd51e2d0d..ee1d3ad0481 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -35,54 +35,20 @@ Maven build commands:
## Code Standards
-1. Follow CODE_OF_CONDUCT.md
-2. Generate minimal essential code only
-3. Prioritize readability & scalability, avoid over-engineering
-
-## Quality Assurance Standards
-
-### Code Quality Requirements
-
-1. **Minimal Essential Code**: Write only the code needed to fulfill
requirements
- - Eliminate redundant variables, methods, and logic
- - Remove dead code and unused imports
- - Prefer concise expressions over verbose implementations
-
-2. **Readability First**: Code must be self-documenting and immediately
understandable
- - Use clear, descriptive variable and method names
- - Write code that reads like natural language
- - Add comments only when business logic is complex or non-obvious
- - Structure code to minimize cognitive load
-
-3. **Performance Considerations**: Consider execution efficiency in all
implementations
- - Optimize algorithms for optimal time/space complexity
- - Consider execution frequency and critical path optimization
- - Minimize resource consumption (memory, CPU, I/O)
- - Avoid unnecessary object creation and method calls in hot paths
- - Use appropriate data structures for the use case
- - Consider lazy evaluation where beneficial
-
-### Testing Standards
-
-1. **Coverage Requirements**:
- - 100% line coverage for all new code
- - 100% branch coverage where logically possible
- - Test all edge cases and error conditions
- - Validate both positive and negative scenarios
-
-2. **Test Case Principles**:
- - Each test must validate unique behavior - no redundant tests
- - Use clear, descriptive test names that indicate what is being tested
- - Follow Arrange-Act-Assert pattern consistently
- - Mock external dependencies appropriately
- - Keep tests fast, independent, and deterministic
-
-3. **Test Quality**:
- - Tests should fail for the right reasons and be easy to debug
- - Maintain test readability and maintainability
- - Use parameterized tests for multiple similar scenarios
- - Focus on behavior testing rather than implementation details
- - Ensure tests provide meaningful failure messages
+1. Follow CODE_OF_CONDUCT.md (clean code principles, naming conventions,
formatting)
+2. **AI-Specific Requirements**:
+ - Generate minimal essential code only
+ - Prioritize readability as highest priority
+ - Consider extreme performance optimization
+3. Prioritize scalability, avoid over-engineering
+
+## Testing Standards
+
+1. Follow CODE_OF_CONDUCT.md (AIR principle, BCDE design, naming conventions)
+2. **AI-Specific Requirements**:
+ - 100% line and branch coverage for all new code
+ - No redundant test cases - each test validates unique behavior
+ - Focus on behavior testing over implementation details
## Absolute Prohibitions (Zero-Tolerance)
