oh-my-customcode 0.19.3 → 0.19.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oh-my-customcode",
-  "version": "0.19.3",
+  "version": "0.19.4",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/hooks/scripts/session-env-check.sh

@@ -27,16 +27,34 @@ if [ "${CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS:-0}" = "1" ]; then
   AGENT_TEAMS_STATUS="enabled"
 fi
 
+# Git workflow reminder
+CURRENT_BRANCH="unknown"
+if command -v git >/dev/null 2>&1 && git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
+  CURRENT_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
+fi
+
 # Write status to file for other hooks to reference
 STATUS_FILE="/tmp/.claude-env-status-${PPID}"
 cat > "$STATUS_FILE" << ENVEOF
 codex=${CODEX_STATUS}
 agent_teams=${AGENT_TEAMS_STATUS}
+git_branch=${CURRENT_BRANCH}
 ENVEOF
 
 # Report to stderr (visible in conversation)
 echo "  codex CLI: ${CODEX_STATUS}" >&2
 echo "  Agent Teams: ${AGENT_TEAMS_STATUS}" >&2
+echo "" >&2
+echo "  [Git Workflow Reminder]" >&2
+echo "  Current branch: ${CURRENT_BRANCH}" >&2
+if [ "$CURRENT_BRANCH" = "develop" ] || [ "$CURRENT_BRANCH" = "main" ] || [ "$CURRENT_BRANCH" = "master" ]; then
+  echo "  ⚠ You are on a protected branch!" >&2
+  echo "  ⚠ Create a feature branch before making changes:" >&2
+  echo "    git checkout -b feat/your-feature develop" >&2
+else
+  echo "  ✓ Feature branch detected" >&2
+fi
+echo "  Rules: feature branch → commit → push → PR → merge" >&2
 echo "------------------------------------" >&2
 
 # Pass through

package/templates/.claude/rules/MUST-agent-teams.md

@@ -48,6 +48,28 @@ BEFORE using Task tool for 2+ agent tasks, this check is **ENFORCED**:
 ╚══════════════════════════════════════════════════════════════════╝
 ```
 
+### Spawn Completeness Check (MANDATORY)
+
+When spawning Agent Teams members:
+
+**ALL members MUST be spawned in a SINGLE message.** Partial spawning is a VIOLATION of both R018 and R009.
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  BEFORE SPAWNING TEAM MEMBERS:                                   ║
+║                                                                   ║
+║  1. How many members does this team need?  N = ___               ║
+║  2. Am I spawning ALL N members in THIS message?                 ║
+║     YES → Good. Continue.                                        ║
+║     NO  → STOP. This is a VIOLATION.                             ║
+║           All N members MUST be in the same message.             ║
+║                                                                   ║
+║  Partial spawn (e.g., 1/3) = VIOLATION                           ║
+║  Sequential spawn (one per message) = VIOLATION                  ║
+║  All at once in single message = CORRECT                         ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
 ## Common Violations
 
 ```
@@ -87,6 +109,19 @@ BEFORE using Task tool for 2+ agent tasks, this check is **ENFORCED**:
    Task(frontend-dev) + Task(backend-dev) → team members
    Shared TaskList for interface contracts
    SendMessage for API schema coordination
+
+❌ WRONG: Spawning team members one at a time
+   TeamCreate("research-team")
+   Message 1: Task(researcher-1) → Analysis 1   (only 1/3 spawned)
+   Message 2: Task(researcher-2) → Analysis 2   (late spawn)
+   Message 3: Task(researcher-3) → Analysis 3   (late spawn)
+
+✓ CORRECT: All members in a single message
+   TeamCreate("research-team")
+   Single message:
+     Task(researcher-1) → Analysis 1  ┐
+     Task(researcher-2) → Analysis 2  ├─ ALL spawned together
+     Task(researcher-3) → Analysis 3  ┘
 ```
 
 ## Cost Guidelines

package/templates/.claude/rules/MUST-parallel-execution.md

@@ -39,6 +39,7 @@ Before writing/editing multiple files:
 2. Using Write/Edit sequentially for 2+ files? → STOP, parallelize
 3. Specialized agent available? → Use it (not general-purpose)
 4. Agent Teams available + 3+ agents or review cycle? → YES: use Agent Teams instead of Task
+5. Agent Teams members? → ALL members MUST spawn in a single message (no partial spawning)
 
 ### Common Violations to Avoid
 
@@ -79,6 +80,18 @@ Before writing/editing multiple files:
    Task(lang-kotlin-expert → usecase queries)     ├─ All spawned together
    Task(be-springboot-expert → persistence)       │
    Task(be-springboot-expert → security)          ┘
+
+❌ WRONG: Agent Teams partial spawn (1 of N members)
+   TeamCreate("feature-team")
+   Message 1: Task(member-1)  ← only 1/3 spawned, VIOLATION
+   Message 2: Task(member-2)  ← sequential, VIOLATION
+   Message 3: Task(member-3)  ← sequential, VIOLATION
+
+✓ CORRECT: All Agent Teams members in single message
+   TeamCreate("feature-team")
+   Task(member-1)  ┐
+   Task(member-2)  ├─ Single message, all at once
+   Task(member-3)  ┘
 ```
 
 ## Execution Rules