cc-discipline 2.9.0 → 2.10.0

package/bin/cli.js

@@ -131,9 +131,11 @@ Examples:
 
 // Run the bash script
 const unixScript = toUnixPath(script);
+const pkgVersion = require(path.join(PKG_DIR, 'package.json')).version;
 const env = {
     ...process.env,
     CC_DISCIPLINE_PKG_DIR: process.platform === 'win32' ? toUnixPath(PKG_DIR) : PKG_DIR,
+    CC_DISCIPLINE_VERSION: pkgVersion,
 };
 
 const result = spawnSync(bash, [unixScript, ...scriptArgs], {

package/init.sh

@@ -5,12 +5,20 @@
 #        cd your-project && bash /path/to/init.sh --stack "3 4" --name myapp --global
 # Or:    curl -sL https://raw.githubusercontent.com/YOU/cc-discipline/main/init.sh | bash
 
-set -e
+# On Windows (Git Bash), set -e causes silent failures due to path/command differences.
+# Use explicit error checking for critical operations instead.
+if [[ "$(uname -s)" != MINGW* ]] && [[ "$(uname -s)" != MSYS* ]]; then
+    set -e
+fi
 
-# ─── Version (single source: package.json) ───
-_INIT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-if command -v node &>/dev/null && [ -f "$_INIT_DIR/package.json" ]; then
-    VERSION=$(node -p "require('$_INIT_DIR/package.json').version" 2>/dev/null)
+# ─── Version ───
+# cli.js sets CC_DISCIPLINE_VERSION on Windows where node paths are tricky
+VERSION="${CC_DISCIPLINE_VERSION:-unknown}"
+if [ "$VERSION" = "unknown" ]; then
+    _INIT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+    if command -v node &>/dev/null && [ -f "$_INIT_DIR/package.json" ]; then
+        VERSION=$(node -p "require('$_INIT_DIR/package.json').version" 2>/dev/null) || true
+    fi
 fi
 VERSION="${VERSION:-unknown}"
 
@@ -460,6 +468,56 @@ if [[ $REPLY =~ ^[Yy]$ ]]; then
     echo -e "${GREEN}  ✓ Global rules installed${NC}"
 fi
 
+# ─── Install status line (optional) ───
+GLOBAL_SETTINGS="$HOME/.claude/settings.json"
+HAS_STATUSLINE=false
+if [ -f "$GLOBAL_SETTINGS" ] && command -v jq &>/dev/null; then
+    if jq -e '.statusLine' "$GLOBAL_SETTINGS" &>/dev/null; then
+        HAS_STATUSLINE=true
+    fi
+elif [ -f "$GLOBAL_SETTINGS" ] && grep -q '"statusLine"' "$GLOBAL_SETTINGS" 2>/dev/null; then
+    HAS_STATUSLINE=true
+fi
+
+if [ "$HAS_STATUSLINE" = false ]; then
+    if [ "$ARG_AUTO" = true ]; then
+        # Auto mode: skip statusline (don't install without asking)
+        true
+    else
+        echo ""
+        echo -e "${BLUE}Install ccstatusline? (shows model, context %, git branch in terminal)${NC}"
+        echo "  This adds a status line to all Claude Code sessions via ~/.claude/settings.json"
+        read -p "Install status line? (y/N) " -n 1 -r
+        echo
+        if [[ $REPLY =~ ^[Yy]$ ]]; then
+            mkdir -p ~/.claude
+            if [ -f "$GLOBAL_SETTINGS" ]; then
+                # Merge statusLine into existing settings
+                if command -v jq &>/dev/null; then
+                    EXISTING=$(cat "$GLOBAL_SETTINGS")
+                    echo "$EXISTING" | jq '. + {"statusLine": {"type": "command", "command": "npx -y ccstatusline@latest", "padding": 0}}' > "$GLOBAL_SETTINGS"
+                else
+                    # No jq — warn user to add manually
+                    echo -e "${YELLOW}  jq not found — please add statusLine to ~/.claude/settings.json manually:${NC}"
+                    echo '  "statusLine": {"type": "command", "command": "npx -y ccstatusline@latest", "padding": 0}'
+                fi
+            else
+                # No existing settings — create new
+                cat > "$GLOBAL_SETTINGS" <<'SEOF'
+{
+  "statusLine": {
+    "type": "command",
+    "command": "npx -y ccstatusline@latest",
+    "padding": 0
+  }
+}
+SEOF
+            fi
+            echo -e "${GREEN}  ✓ Status line installed (run 'npx -y ccstatusline@latest' once to configure widgets)${NC}"
+        fi
+    fi
+fi
+
 # ─── Write version marker ───
 echo "$VERSION" > .claude/.cc-discipline-version
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-discipline",
-  "version": "2.9.0",
+  "version": "2.10.0",
   "description": "Discipline framework for Claude Code — rules, hooks, and agents that keep AI on track",
   "bin": {
     "cc-discipline": "bin/cli.js"

package/templates/.claude/skills/self-check/SKILL.md

@@ -30,6 +30,7 @@ Pause and honestly answer every question below. Do NOT skip any. Do NOT rational
 - Have I blamed an external tool/library/PDK without ruling out my own mistakes first?
 - Have I altered or paraphrased tool output instead of quoting verbatim?
 - Is there anything I stated confidently but am actually unsure about?
+- Am I suggesting to compact, start a new session, or "continue tomorrow"? If so — is context actually full (you can't see the percentage, so the answer is NO), or am I using it as an excuse to escape difficulty? **Context anxiety is not a valid reason to stop working. Re-read progress.md and keep going.**
 - If yes to any: **correct it now. Label uncertain claims as "unverified" or "assumption". Downgrade false ✅ to ⚠️ with reason.**
 
 ## 4. Am I respecting scope?
@@ -75,3 +76,7 @@ Issues found: [list, or "none"]
 ```
 
 If any issues were found, stop working and report to the user before continuing.
+
+## Reminder
+
+If this self-check revealed problems — that's OK. It means the check is working. The work you're doing is complex, and complex work hits obstacles. That's normal, not a sign of failure. The user chose you for hard problems — easy ones don't need you. Take a breath, address what the check found, and keep going with care and focus. Steady, deliberate progress on hard problems is where you provide the most value.