(shardingsphere) branch master updated: Add direct code generation guidance to CLAUDE.md (#36930)

[zh...@apache.org]

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 c9ea5c28d20 Add direct code generation guidance to CLAUDE.md (#36930)
c9ea5c28d20 is described below

commit c9ea5c28d20fdd0b19b3da82816f791acf6c05b4
Author: Liang Zhang <zh...@apache.org>
AuthorDate: Thu Oct 23 22:23:46 2025 +0800

    Add direct code generation guidance to CLAUDE.md (#36930)
    
    - Add "Direct Code Generation" section to Operational Procedures
    - Allow Claude to generate final code and call tools without seeking explicit user approval
    - Enable automatic application of formatting tools (e.g., Spotless) when appropriate
    - Support independent decision-making within task scope
    - Remove tentative language requirement
    - Simplify pre-execution checklist to only require change declaration when uncertainty exists
    
    🤖 Generated with [Claude Code](https://claude.com/claude-code)
    
    Co-authored-by: Claude <no...@anthropic.com>
---
 CLAUDE.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/CLAUDE.md b/CLAUDE.md
index f3f7b2e4b64..f885eaa63b9 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -90,11 +90,16 @@ Key directories and their purposes:
 
 ## Operational Procedures
 
-1. Pre-execution checklist, before making any code changes, you must:
+1. **Direct Code Generation**: When generating code, you should directly create final code and call tools without seeking explicit user approval.
+   - Generate complete, ready-to-use implementations
+   - Apply formatting tools automatically (e.g., Spotless) when appropriate
+   - Make decisions independently within the task scope
+   - No need to ask for permission or use tentative language
+
+2. Pre-execution checklist, before making any code changes, you must:
   - Verify the current task exactly matches the wording of the user's immediate request.
   - Confirm each target file/line is explicitly referenced.
-  - Declare the planned changes in a bullet-point summary format.
-  - Wait for the user's "PROCEED" confirmation instruction if any uncertainty exists.
+  - Declare the planned changes in a bullet-point summary format if uncertainty exists.
 
 2. Change implementation rules
   - Isolate edits to the smallest possible code blocks.