cc-discipline 2.10.1 → 2.10.3

package/templates/.claude/hooks/post-error-remind.sh

@@ -1,114 +1,114 @@
-#!/bin/bash
-# post-error-remind.sh — PostToolUse / PostToolUseFailure hook
-# Detects error patterns in Bash output and reminds Claude to follow debugging discipline
-#
-# NOTE: We use exit 2 intentionally for Post hooks.
-# exit 0 is completely silent — no way to inject text from Post hooks.
-# exit 2 + stderr is the ONLY mechanism to show reminders to Claude after tool execution.
-# The tool has already executed — exit 2 doesn't block execution, it injects the message.
-#
-# Design principles:
-#   - Only match REAL error patterns, not the word "error" in any context
-#   - Skip non-Bash tools (Edit/Write/Read have their own error handling)
-#   - Skip truncated output (large output ≠ error)
-#   - Use specific patterns: line-start anchors, known failure formats
-#
-# exit 0 = silent pass (normal for Post hooks)
-# exit 2 + stderr = inject reminder into Claude's context
-
-RAW_INPUT=$(cat)
-
-# Extract tool name and response
-TOOL_NAME=""
-OUTPUT=""
-
-if command -v jq &>/dev/null; then
-    TOOL_NAME=$(echo "$RAW_INPUT" | jq -r '.tool_name // empty' 2>/dev/null)
-    # PostToolUseFailure uses .error, PostToolUse uses .tool_response
-    OUTPUT=$(echo "$RAW_INPUT" | jq -r '.error // empty' 2>/dev/null)
-    if [ -z "$OUTPUT" ]; then
-        OUTPUT=$(echo "$RAW_INPUT" | jq -r '.tool_response.output // empty' 2>/dev/null)
-    fi
-fi
-
-# Fallback if jq unavailable
-if [ -z "$OUTPUT" ]; then
-    OUTPUT="$RAW_INPUT"
-fi
-
-# --- Early exits for known non-error situations ---
-
-# Only check Bash tool output
-if [ -n "$TOOL_NAME" ] && [ "$TOOL_NAME" != "Bash" ]; then
-    exit 0
-fi
-
-# Truncated output is not an error
-if echo "$OUTPUT" | grep -q "Output too large"; then
-    exit 0
-fi
-
-# Successful git operations
-if echo "$OUTPUT" | grep -qE "^\[main |^\[master |^On branch |^nothing to commit|^Already up to date"; then
-    exit 0
-fi
-
-# --- Detect REAL error patterns ---
-
-HAS_ERROR=false
-ERROR_TYPE=""
-
-# Build/compile errors (line-start or known formats)
-if echo "$OUTPUT" | grep -qE "^ERROR |^\[ERROR\]|BUILD FAILURE|compilation error|cannot find symbol|package .* does not exist"; then
-    HAS_ERROR=true
-    ERROR_TYPE="build"
-fi
-
-# Test failures (Maven/Gradle/Jest specific formats)
-if echo "$OUTPUT" | grep -qE "Tests run:.*Failures: [1-9]|Tests:.*failed|FAILED!|BUILD FAILURE.*test"; then
-    HAS_ERROR=true
-    ERROR_TYPE="test"
-fi
-
-# Runtime crashes
-if echo "$OUTPUT" | grep -qiE "segmentation fault|bus error|core dumped|SIGABRT|SIGSEGV|killed.*signal"; then
-    HAS_ERROR=true
-    ERROR_TYPE="crash"
-fi
-
-# Shell errors (command failures)
-if echo "$OUTPUT" | grep -qE "command not found|permission denied|cannot execute|not a git repository"; then
-    HAS_ERROR=true
-    ERROR_TYPE="system"
-fi
-
-# Stack traces (Java, Python, Node)
-if echo "$OUTPUT" | grep -qE "^Exception in thread|^Traceback \(most recent|^Caused by:.*Exception"; then
-    HAS_ERROR=true
-    ERROR_TYPE="exception"
-fi
-
-# npm/yarn explicit failure
-if echo "$OUTPUT" | grep -qE "^npm ERR!|^error .*ENOENT|FATAL ERROR"; then
-    HAS_ERROR=true
-    ERROR_TYPE="build"
-fi
-
-# --- Emit reminder if error detected ---
-
-if [ "$HAS_ERROR" = true ]; then
-    REMINDER="Error encountered — debugging checklist: 1. Resist modifying code immediately 2. Fully understand the error message 3. List >=3 possible causes — label them hypotheses, not root cause 4. Record in docs/debug-log.md 5. Eliminate >=2 hypotheses with evidence before identifying root cause 6. Only then fix. Important: after seeing one error, the first explanation is a hypothesis, not a conclusion. Say 'possible cause' until you have elimination evidence."
-
-    if [ "$ERROR_TYPE" = "test" ]; then
-        REMINDER="$REMINDER Note: Test failure — before changing the test, first determine if it's a code bug or an outdated test."
-    fi
-
-    if [ "$ERROR_TYPE" = "crash" ]; then
-        REMINDER="$REMINDER Note: Crash/segfault — may involve memory issues."
-    fi
-
-    echo "$REMINDER" >&2
-    exit 2
-fi
-
-exit 0
+#!/bin/bash
+# post-error-remind.sh — PostToolUse / PostToolUseFailure hook
+# Detects error patterns in Bash output and reminds Claude to follow debugging discipline
+#
+# NOTE: We use exit 2 intentionally for Post hooks.
+# exit 0 is completely silent — no way to inject text from Post hooks.
+# exit 2 + stderr is the ONLY mechanism to show reminders to Claude after tool execution.
+# The tool has already executed — exit 2 doesn't block execution, it injects the message.
+#
+# Design principles:
+#   - Only match REAL error patterns, not the word "error" in any context
+#   - Skip non-Bash tools (Edit/Write/Read have their own error handling)
+#   - Skip truncated output (large output ≠ error)
+#   - Use specific patterns: line-start anchors, known failure formats
+#
+# exit 0 = silent pass (normal for Post hooks)
+# exit 2 + stderr = inject reminder into Claude's context
+
+RAW_INPUT=$(cat)
+
+# Extract tool name and response
+TOOL_NAME=""
+OUTPUT=""
+
+if command -v jq &>/dev/null; then
+    TOOL_NAME=$(echo "$RAW_INPUT" | jq -r '.tool_name // empty' 2>/dev/null)
+    # PostToolUseFailure uses .error, PostToolUse uses .tool_response
+    OUTPUT=$(echo "$RAW_INPUT" | jq -r '.error // empty' 2>/dev/null)
+    if [ -z "$OUTPUT" ]; then
+        OUTPUT=$(echo "$RAW_INPUT" | jq -r '.tool_response.output // empty' 2>/dev/null)
+    fi
+fi
+
+# Fallback if jq unavailable
+if [ -z "$OUTPUT" ]; then
+    OUTPUT="$RAW_INPUT"
+fi
+
+# --- Early exits for known non-error situations ---
+
+# Only check Bash tool output
+if [ -n "$TOOL_NAME" ] && [ "$TOOL_NAME" != "Bash" ]; then
+    exit 0
+fi
+
+# Truncated output is not an error
+if echo "$OUTPUT" | grep -q "Output too large"; then
+    exit 0
+fi
+
+# Successful git operations
+if echo "$OUTPUT" | grep -qE "^\[main |^\[master |^On branch |^nothing to commit|^Already up to date"; then
+    exit 0
+fi
+
+# --- Detect REAL error patterns ---
+
+HAS_ERROR=false
+ERROR_TYPE=""
+
+# Build/compile errors (line-start or known formats)
+if echo "$OUTPUT" | grep -qE "^ERROR |^\[ERROR\]|BUILD FAILURE|compilation error|cannot find symbol|package .* does not exist"; then
+    HAS_ERROR=true
+    ERROR_TYPE="build"
+fi
+
+# Test failures (Maven/Gradle/Jest specific formats)
+if echo "$OUTPUT" | grep -qE "Tests run:.*Failures: [1-9]|Tests:.*failed|FAILED!|BUILD FAILURE.*test"; then
+    HAS_ERROR=true
+    ERROR_TYPE="test"
+fi
+
+# Runtime crashes
+if echo "$OUTPUT" | grep -qiE "segmentation fault|bus error|core dumped|SIGABRT|SIGSEGV|killed.*signal"; then
+    HAS_ERROR=true
+    ERROR_TYPE="crash"
+fi
+
+# Shell errors (command failures)
+if echo "$OUTPUT" | grep -qE "command not found|permission denied|cannot execute|not a git repository"; then
+    HAS_ERROR=true
+    ERROR_TYPE="system"
+fi
+
+# Stack traces (Java, Python, Node)
+if echo "$OUTPUT" | grep -qE "^Exception in thread|^Traceback \(most recent|^Caused by:.*Exception"; then
+    HAS_ERROR=true
+    ERROR_TYPE="exception"
+fi
+
+# npm/yarn explicit failure
+if echo "$OUTPUT" | grep -qE "^npm ERR!|^error .*ENOENT|FATAL ERROR"; then
+    HAS_ERROR=true
+    ERROR_TYPE="build"
+fi
+
+# --- Emit reminder if error detected ---
+
+if [ "$HAS_ERROR" = true ]; then
+    REMINDER="Error encountered — debugging checklist: 1. Resist modifying code immediately 2. Fully understand the error message 3. List >=3 possible causes — label them hypotheses, not root cause 4. Record in docs/debug-log.md 5. Eliminate >=2 hypotheses with evidence before identifying root cause 6. Only then fix. Important: after seeing one error, the first explanation is a hypothesis, not a conclusion. Say 'possible cause' until you have elimination evidence."
+
+    if [ "$ERROR_TYPE" = "test" ]; then
+        REMINDER="$REMINDER Note: Test failure — before changing the test, first determine if it's a code bug or an outdated test."
+    fi
+
+    if [ "$ERROR_TYPE" = "crash" ]; then
+        REMINDER="$REMINDER Note: Crash/segfault — may involve memory issues."
+    fi
+
+    echo "$REMINDER" >&2
+    exit 2
+fi
+
+exit 0

package/templates/.claude/hooks/pre-edit-guard.sh

@@ -1,100 +1,100 @@
-#!/bin/bash
-# pre-edit-guard.sh — PreToolUse hook
-# Checks that Claude has finished debugging before editing source code
-#
-# Exit 0 + no output = allow edit
-# Exit 2 + stderr = block edit, stderr shown to Claude
-
-# Read the tool input from stdin (JSON)
-INPUT=$(cat)
-
-# Extract fields
-if command -v jq &>/dev/null; then
-    FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty' 2>/dev/null)
-    CWD=$(echo "$INPUT" | jq -r '.cwd // empty' 2>/dev/null)
-else
-    FILE_PATH=$(echo "$INPUT" | grep -o '"file_path":\s*"[^"]*"' | head -1 | sed 's/"file_path":\s*"//;s/"//')
-    CWD=$(echo "$INPUT" | grep -o '"cwd":\s*"[^"]*"' | head -1 | sed 's/"cwd":\s*"//;s/"//')
-fi
-
-# Extract just the filename for pattern matching (avoid false matches on directory names)
-BASENAME=$(basename "$FILE_PATH")
-
-# Allow edits to docs/
-# Note: use -E (extended regex) for portability — BSD grep (macOS) doesn't support \| in basic mode
-if echo "$FILE_PATH" | grep -qE "^docs/|/docs/"; then
-    exit 0
-fi
-
-# Allow edits to test files (match filename only, not directory path)
-if echo "$BASENAME" | grep -qiE "test|spec"; then
-    exit 0
-fi
-
-# Allow edits to config/meta files
-if echo "$BASENAME" | grep -qiE "\.(md|json|yaml|yml|toml|cfg|ini)$"; then
-    exit 0
-fi
-
-# Check for unresolved hypotheses in debug-log.md
-DEBUG_LOG=""
-if [ -n "$CWD" ] && [ -f "$CWD/docs/debug-log.md" ]; then
-    DEBUG_LOG="$CWD/docs/debug-log.md"
-elif [ -f "docs/debug-log.md" ]; then
-    DEBUG_LOG="docs/debug-log.md"
-fi
-
-if [ -n "$DEBUG_LOG" ]; then
-    # Count only in actual table rows, strip HTML comments (both single-line and multi-line)
-    CLEAN=$(awk '/<!--.*-->/{next} /<!--/{skip=1} /-->/{skip=0;next} !skip{print}' "$DEBUG_LOG" 2>/dev/null)
-    PENDING=$(echo "$CLEAN" | grep -c '| pending |' 2>/dev/null) || PENDING=0
-    CONFIRMED=$(echo "$CLEAN" | grep -c '| confirmed |' 2>/dev/null) || CONFIRMED=0
-
-    if [ "$PENDING" -gt "$CONFIRMED" ] 2>/dev/null; then
-        cat >&2 <<EOF
-docs/debug-log.md has $((PENDING - CONFIRMED)) unverified hypotheses.
-Please complete the debugging process (verify or eliminate hypotheses) before editing source code.
-If you have confirmed the root cause, update debug-log.md first.
-EOF
-        exit 2
-    fi
-fi
-
-# ─── Large diff warning ───
-HAS_JQ=false
-command -v jq &>/dev/null && HAS_JQ=true
-
-if [ "$HAS_JQ" = true ]; then
-    NEW_STRING=$(echo "$INPUT" | jq -r '.tool_input.new_string // ""')
-    OLD_STRING=$(echo "$INPUT" | jq -r '.tool_input.old_string // ""')
-    NEW_LINES=$(echo "$NEW_STRING" | wc -l | tr -d ' ')
-    OLD_LINES=$(echo "$OLD_STRING" | wc -l | tr -d ' ')
-    DIFF_LINES=$((NEW_LINES > OLD_LINES ? NEW_LINES : OLD_LINES))
-    if [ "$DIFF_LINES" -gt 200 ]; then
-        echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"additionalContext\":\"LARGE EDIT NOTE: This edit involves ${DIFF_LINES} lines. Consider: is this the minimal change needed? Could it be broken into smaller, more focused edits?\"}}"
-        exit 0
-    fi
-fi
-
-# ─── New tool/script detection ───
-# When creating a script file via Write, remind to register in CLAUDE.md
-TOOL_NAME=$(echo "$INPUT" | jq -r '.tool_name // empty' 2>/dev/null)
-if [ "$TOOL_NAME" = "Write" ] && echo "$BASENAME" | grep -qiE "\.(sh|py|js|ts|rb|pl)$"; then
-    # Check if file already exists (new file = tool creation)
-    FULL_PATH="$FILE_PATH"
-    if [ ! -f "$FULL_PATH" ]; then
-        cat <<JSONEOF
-{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"NEW SCRIPT DETECTED: You are creating $BASENAME. If this is a reusable tool/helper, register it in CLAUDE.md under 'Project Tools' now (path, purpose, usage, date) — capturing it while context is fresh saves time later."}}
-JSONEOF
-        exit 0
-    fi
-fi
-
-# ─── Bug-fix sanity check ───
-# Inject a lightweight reminder on source file edits:
-# "If this is a bug fix, have you eliminated alternative hypotheses?"
-# Uses additionalContext (non-blocking) so it doesn't slow down normal edits.
-cat <<JSONEOF
-{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"If this edit is a bug fix: have you listed >=3 possible causes and eliminated >=2 with evidence? Thorough elimination before fixing prevents wasted cycles. Use 'possible cause' until elimination evidence confirms the root cause."}}
-JSONEOF
-exit 0
+#!/bin/bash
+# pre-edit-guard.sh — PreToolUse hook
+# Checks that Claude has finished debugging before editing source code
+#
+# Exit 0 + no output = allow edit
+# Exit 2 + stderr = block edit, stderr shown to Claude
+
+# Read the tool input from stdin (JSON)
+INPUT=$(cat)
+
+# Extract fields
+if command -v jq &>/dev/null; then
+    FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty' 2>/dev/null)
+    CWD=$(echo "$INPUT" | jq -r '.cwd // empty' 2>/dev/null)
+else
+    FILE_PATH=$(echo "$INPUT" | grep -o '"file_path":\s*"[^"]*"' | head -1 | sed 's/"file_path":\s*"//;s/"//')
+    CWD=$(echo "$INPUT" | grep -o '"cwd":\s*"[^"]*"' | head -1 | sed 's/"cwd":\s*"//;s/"//')
+fi
+
+# Extract just the filename for pattern matching (avoid false matches on directory names)
+BASENAME=$(basename "$FILE_PATH")
+
+# Allow edits to docs/
+# Note: use -E (extended regex) for portability — BSD grep (macOS) doesn't support \| in basic mode
+if echo "$FILE_PATH" | grep -qE "^docs/|/docs/"; then
+    exit 0
+fi
+
+# Allow edits to test files (match filename only, not directory path)
+if echo "$BASENAME" | grep -qiE "test|spec"; then
+    exit 0
+fi
+
+# Allow edits to config/meta files
+if echo "$BASENAME" | grep -qiE "\.(md|json|yaml|yml|toml|cfg|ini)$"; then
+    exit 0
+fi
+
+# Check for unresolved hypotheses in debug-log.md
+DEBUG_LOG=""
+if [ -n "$CWD" ] && [ -f "$CWD/docs/debug-log.md" ]; then
+    DEBUG_LOG="$CWD/docs/debug-log.md"
+elif [ -f "docs/debug-log.md" ]; then
+    DEBUG_LOG="docs/debug-log.md"
+fi
+
+if [ -n "$DEBUG_LOG" ]; then
+    # Count only in actual table rows, strip HTML comments (both single-line and multi-line)
+    CLEAN=$(awk '/<!--.*-->/{next} /<!--/{skip=1} /-->/{skip=0;next} !skip{print}' "$DEBUG_LOG" 2>/dev/null)
+    PENDING=$(echo "$CLEAN" | grep -c '| pending |' 2>/dev/null) || PENDING=0
+    CONFIRMED=$(echo "$CLEAN" | grep -c '| confirmed |' 2>/dev/null) || CONFIRMED=0
+
+    if [ "$PENDING" -gt "$CONFIRMED" ] 2>/dev/null; then
+        cat >&2 <<EOF
+docs/debug-log.md has $((PENDING - CONFIRMED)) unverified hypotheses.
+Please complete the debugging process (verify or eliminate hypotheses) before editing source code.
+If you have confirmed the root cause, update debug-log.md first.
+EOF
+        exit 2
+    fi
+fi
+
+# ─── Large diff warning ───
+HAS_JQ=false
+command -v jq &>/dev/null && HAS_JQ=true
+
+if [ "$HAS_JQ" = true ]; then
+    NEW_STRING=$(echo "$INPUT" | jq -r '.tool_input.new_string // ""')
+    OLD_STRING=$(echo "$INPUT" | jq -r '.tool_input.old_string // ""')
+    NEW_LINES=$(echo "$NEW_STRING" | wc -l | tr -d ' ')
+    OLD_LINES=$(echo "$OLD_STRING" | wc -l | tr -d ' ')
+    DIFF_LINES=$((NEW_LINES > OLD_LINES ? NEW_LINES : OLD_LINES))
+    if [ "$DIFF_LINES" -gt 200 ]; then
+        echo "{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"additionalContext\":\"LARGE EDIT NOTE: This edit involves ${DIFF_LINES} lines. Consider: is this the minimal change needed? Could it be broken into smaller, more focused edits?\"}}"
+        exit 0
+    fi
+fi
+
+# ─── New tool/script detection ───
+# When creating a script file via Write, remind to register in CLAUDE.md
+TOOL_NAME=$(echo "$INPUT" | jq -r '.tool_name // empty' 2>/dev/null)
+if [ "$TOOL_NAME" = "Write" ] && echo "$BASENAME" | grep -qiE "\.(sh|py|js|ts|rb|pl)$"; then
+    # Check if file already exists (new file = tool creation)
+    FULL_PATH="$FILE_PATH"
+    if [ ! -f "$FULL_PATH" ]; then
+        cat <<JSONEOF
+{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"NEW SCRIPT DETECTED: You are creating $BASENAME. If this is a reusable tool/helper, register it in CLAUDE.md under 'Project Tools' now (path, purpose, usage, date) — capturing it while context is fresh saves time later."}}
+JSONEOF
+        exit 0
+    fi
+fi
+
+# ─── Bug-fix sanity check ───
+# Inject a lightweight reminder on source file edits:
+# "If this is a bug fix, have you eliminated alternative hypotheses?"
+# Uses additionalContext (non-blocking) so it doesn't slow down normal edits.
+cat <<JSONEOF
+{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"If this edit is a bug fix: have you listed >=3 possible causes and eliminated >=2 with evidence? Thorough elimination before fixing prevents wasted cycles. Use 'possible cause' until elimination evidence confirms the root cause."}}
+JSONEOF
+exit 0

package/templates/.claude/hooks/session-start.sh

@@ -1,44 +1,44 @@
-#!/bin/bash
-# cc-discipline: SessionStart hook
-# Injects project state + discipline reminders into Claude's context.
-# stdout → context (Claude can see and act on it)
-# Fires on: startup, resume, clear, compact
-
-# Reset action counter for this session
-INPUT=$(cat)
-SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // "unknown"' 2>/dev/null)
-if [ -n "$SESSION_ID" ] && [ "$SESSION_ID" != "unknown" ]; then
-    rm -f "/tmp/cc-discipline-${SESSION_ID}/action-count"
-fi
-
-# Read project state
-PROGRESS=""
-if [ -f "docs/progress.md" ]; then
-    PROGRESS=$(tail -20 docs/progress.md)
-fi
-
-cat <<'HEADER'
-[cc-discipline] Session initialized.
-HEADER
-
-if [ -n "$PROGRESS" ]; then
-cat <<EOF
-
-Project state (from docs/progress.md):
-$PROGRESS
-
-Verify project status by reading files or asking — don't assume beyond what is stated above.
-EOF
-fi
-
-cat <<'EOF'
-
-Reminders:
-- /self-check available for periodic monitoring. For complex tasks: /loop 10m /self-check
-- Before editing: root cause identified? scope respected? change recorded?
-- 3 consecutive failures → pause and regroup with the user
-- Confirm the approach with the user before starting implementation
-- Verify project state (phase, status, dependencies) by reading files or asking
-EOF
-
-exit 0
+#!/bin/bash
+# cc-discipline: SessionStart hook
+# Injects project state + discipline reminders into Claude's context.
+# stdout → context (Claude can see and act on it)
+# Fires on: startup, resume, clear, compact
+
+# Reset action counter for this session
+INPUT=$(cat)
+SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // "unknown"' 2>/dev/null)
+if [ -n "$SESSION_ID" ] && [ "$SESSION_ID" != "unknown" ]; then
+    rm -f "/tmp/cc-discipline-${SESSION_ID}/action-count"
+fi
+
+# Read project state
+PROGRESS=""
+if [ -f "docs/progress.md" ]; then
+    PROGRESS=$(tail -20 docs/progress.md)
+fi
+
+cat <<'HEADER'
+[cc-discipline] Session initialized.
+HEADER
+
+if [ -n "$PROGRESS" ]; then
+cat <<EOF
+
+Project state (from docs/progress.md):
+$PROGRESS
+
+Verify project status by reading files or asking — don't assume beyond what is stated above.
+EOF
+fi
+
+cat <<'EOF'
+
+Reminders:
+- /self-check available for periodic monitoring. For complex tasks: /loop 10m /self-check
+- Before editing: root cause identified? scope respected? change recorded?
+- 3 consecutive failures → pause and regroup with the user
+- Confirm the approach with the user before starting implementation
+- Verify project state (phase, status, dependencies) by reading files or asking
+EOF
+
+exit 0