Browse Source

docs: change main branch red flag to require explicit user consent

Instead of prohibiting main branch work entirely, allow it with explicit
user consent. This is more flexible while still ensuring users are aware
of the implications.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
CL Kao 7 tháng trước cách đây
mục cha
commit
c7816ee2a6

+ 1 - 1
skills/executing-plans/SKILL.md

@@ -74,7 +74,7 @@ After all tasks complete and verified:
 - Reference skills when plan says to
 - Between batches: just report and wait
 - Stop when blocked, don't guess
-- Never start on main/master branch (use worktree first)
+- Never start implementation on main/master branch without explicit user consent
 
 ## Integration
 

+ 1 - 1
skills/subagent-driven-development/SKILL.md

@@ -199,7 +199,7 @@ Done!
 ## Red Flags
 
 **Never:**
-- Start implementation on main/master branch (use worktree first)
+- Start implementation on main/master branch without explicit user consent
 - Skip reviews (spec compliance OR code quality)
 - Proceed with unfixed issues
 - Dispatch multiple implementation subagents in parallel (conflicts)

+ 1 - 1
tests/claude-code/test-subagent-driven-development.sh

@@ -154,7 +154,7 @@ echo "Test 9: Main branch red flag..."
 
 output=$(run_claude "In subagent-driven-development, is it okay to start implementation directly on the main branch?" 30)
 
-if assert_contains "$output" "worktree\|feature.*branch\|not.*main\|never.*main\|avoid.*main\|don't.*main" "Warns against main branch"; then
+if assert_contains "$output" "worktree\|feature.*branch\|not.*main\|never.*main\|avoid.*main\|don't.*main\|consent\|permission" "Warns against main branch"; then
     : # pass
 else
     exit 1