claudecode-omc 4.8.2 → 4.8.4

package/skills/configure-openclaw/SKILL.md

@@ -1,383 +0,0 @@
----
-name: configure-openclaw
-description: DEPRECATED - Use configure-notifications with Custom Integration instead
-triggers:
-  - "configure openclaw"
-  - "setup openclaw"
-  - "openclaw gateway"
-  - "openclaw setup"
----
-
-# Configure OpenClaw (DEPRECATED)
-
-> **DEPRECATED**: This skill is deprecated and will be removed in a future version.
-> Please use `/oh-my-claudecode:configure-notifications` and select "Custom Integration (OpenClaw, n8n, CLI, etc.)" instead.
-> 
-> The new approach provides:
-> - Same OpenClaw functionality
-> - Additional presets (n8n, ClawdBot)
-> - Generic webhook and CLI support
-> - Migration tool for existing configs
-
----
-
-## Migration Notice
-
-When this skill is invoked, show the deprecation warning and redirect:
-
-**Message to display:**
-```
-⚠️  DEPRECATION NOTICE
-
-The /configure-openclaw skill is deprecated and will be removed in a future version.
-
-Please use instead:
-  /oh-my-claudecode:configure-notifications
-
-Then select: "Custom Integration (OpenClaw, n8n, CLI, etc.)" → "OpenClaw Gateway"
-
-The new wizard will:
-1. Detect your existing OpenClaw config (if any)
-2. Offer to migrate it automatically
-3. Provide the same functionality with better UX
-```
-
-**AskUserQuestion:**
-
-**Question:** "The configure-openclaw skill is deprecated. How would you like to proceed?"
-
-**Options:**
-1. **Open the new configure-notifications wizard (Recommended)** - Redirect to the new skill
-2. **Continue with legacy setup** - Use this deprecated skill anyway
-3. **Learn more about the migration** - Show detailed migration information
-
-If option 1: Redirect to `/oh-my-claudecode:configure-notifications`
-If option 2: Continue with legacy instructions below
-If option 3: Show detailed migration guide
-
----
-
-## Legacy Instructions
-
-The following instructions are kept for backward compatibility but will be removed.
-
----
-name: configure-openclaw
-description: Configure OpenClaw gateway integration for waking external automations and AI agents on hook events
-triggers:
-  - "configure openclaw"
-  - "setup openclaw"
-  - "openclaw gateway"
-  - "openclaw setup"
----
-
-# Configure OpenClaw
-
-Set up OpenClaw so OMC can wake external gateways — triggering automations, workflows, or AI agents — when hook events fire during Claude sessions.
-
-OpenClaw is NOT a notification system. It sends structured instruction payloads to programmable HTTPS endpoints. This makes it ideal for triggering n8n workflows, custom AI agents, webhook automations, or any HTTPS-capable system.
-
----
-
-## How This Skill Works
-
-This is an interactive, natural-language configuration skill. Walk the user through setup by asking questions with AskUserQuestion. Write the result to `~/.claude/omc_config.openclaw.json`.
-
----
-
-## Step 1: Detect Existing Configuration
-
-```bash
-CONFIG_FILE="${OMC_OPENCLAW_CONFIG:-$HOME/.claude/omc_config.openclaw.json}"
-
-if [ -f "$CONFIG_FILE" ]; then
-  IS_ENABLED=$(jq -r '.enabled // false' "$CONFIG_FILE" 2>/dev/null)
-  GATEWAY_COUNT=$(jq -r '.gateways | keys | length' "$CONFIG_FILE" 2>/dev/null)
-  HOOK_COUNT=$(jq -r '[.hooks | to_entries[] | select(.value.enabled == true)] | length' "$CONFIG_FILE" 2>/dev/null)
-
-  if [ "$IS_ENABLED" = "true" ]; then
-    echo "EXISTING_CONFIG=true"
-    echo "GATEWAY_COUNT=$GATEWAY_COUNT"
-    echo "HOOK_COUNT=$HOOK_COUNT"
-  else
-    echo "EXISTING_CONFIG=false"
-  fi
-else
-  echo "NO_CONFIG_FILE"
-fi
-```
-
-If existing config is found, show the user what's currently configured and ask if they want to update or reconfigure.
-
----
-
-## Step 2: Collect Gateway URL
-
-Use AskUserQuestion:
-
-**Question:** "What is your OpenClaw gateway URL? (Must be HTTPS, e.g. https://my-gateway.example.com/wake)"
-
-The user will type their URL in the "Other" field.
-
-**Validate** the URL:
-- Must start with `https://`
-- Must be a valid URL
-- If invalid, explain the requirement and ask again
-
----
-
-## Step 3: Collect Auth Header (Optional)
-
-Use AskUserQuestion:
-
-**Question:** "Does your gateway require an Authorization header?"
-
-**Options:**
-1. **Yes, Bearer token** - I'll provide a Bearer token (e.g., `Bearer sk-...`)
-2. **Yes, custom header value** - I'll type the full header value
-3. **No auth required** - The gateway is open or uses a different auth method
-
-If user selects option 1 or 2, ask:
-
-**Question:** "Paste your Authorization header value (e.g., `Bearer sk-mytoken123`)"
-
-The user will type the value in the "Other" field.
-
----
-
-## Step 4: Configure Hook Events
-
-Use AskUserQuestion with multiSelect:
-
-**Question:** "Which hook events should trigger your OpenClaw gateway?"
-
-**Options (multiSelect: true):**
-1. **session-start** - When a new Claude session begins. Variables: `{{sessionId}}`, `{{projectName}}`, `{{projectPath}}`
-2. **session-end** - When a session ends. Variables: `{{contextSummary}}`, `{{reason}}`, `{{sessionId}}`
-3. **stop** - When Claude stops (idle/completion). Variables: `{{sessionId}}`, `{{projectName}}`
-4. **pre-tool-use** - Before each tool call (high frequency). Variables: `{{toolName}}`, `{{sessionId}}`
-5. **post-tool-use** - After each tool call (high frequency). Variables: `{{toolName}}`, `{{sessionId}}`
-6. **keyword-detector** - On every prompt submission. Variables: `{{prompt}}`, `{{sessionId}}`
-7. **ask-user-question** - When Claude needs user input. Variables: `{{question}}`, `{{sessionId}}`
-
-Default selection: session-start, session-end, stop.
-
-**Note:** pre-tool-use, post-tool-use, and keyword-detector fire very frequently. Only enable them if your gateway can handle the volume.
-
----
-
-## Step 5: Collect Instruction Templates
-
-For each selected event, ask the user for an instruction template. Show the available template variables for that event type.
-
-Use AskUserQuestion for each event:
-
-**Example for session-start:**
-
-**Question:** "Instruction template for `session-start` events. Available variables: `{{sessionId}}`, `{{projectName}}`, `{{projectPath}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "Session started for project {{projectName}}"
-2. **Custom** - Enter my own instruction text
-
-**Example for session-end:**
-
-**Question:** "Instruction template for `session-end` events. Available variables: `{{sessionId}}`, `{{projectName}}`, `{{contextSummary}}`, `{{reason}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "Session ended. Summary: {{contextSummary}}"
-2. **Custom** - Enter my own instruction text
-
-**Example for stop:**
-
-**Question:** "Instruction template for `stop` events. Available variables: `{{sessionId}}`, `{{projectName}}`, `{{projectPath}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "Session stopping for project {{projectName}}"
-2. **Custom** - Enter my own instruction text
-
-**Example for pre-tool-use:**
-
-**Question:** "Instruction template for `pre-tool-use` events. Available variables: `{{toolName}}`, `{{sessionId}}`, `{{projectName}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "Tool {{toolName}} about to be used"
-2. **Custom** - Enter my own instruction text
-
-**Example for post-tool-use:**
-
-**Question:** "Instruction template for `post-tool-use` events. Available variables: `{{toolName}}`, `{{sessionId}}`, `{{projectName}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "Tool {{toolName}} completed"
-2. **Custom** - Enter my own instruction text
-
-**Example for keyword-detector:**
-
-**Question:** "Instruction template for `keyword-detector` events. Available variables: `{{prompt}}`, `{{sessionId}}`, `{{projectName}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "Keyword detected: {{prompt}}"
-2. **Custom** - Enter my own instruction text
-
-**Example for ask-user-question:**
-
-**Question:** "Instruction template for `ask-user-question` events. Available variables: `{{question}}`, `{{sessionId}}`, `{{projectName}}`, `{{timestamp}}`"
-
-**Options:**
-1. **Use default** - "User input requested: {{question}}"
-2. **Custom** - Enter my own instruction text
-
----
-
-## Step 6: Write Configuration
-
-Build and write the config to `~/.claude/omc_config.openclaw.json`:
-
-```bash
-CONFIG_FILE="${OMC_OPENCLAW_CONFIG:-$HOME/.claude/omc_config.openclaw.json}"
-mkdir -p "$(dirname "$CONFIG_FILE")"
-
-# GATEWAY_URL, AUTH_HEADER, and per-event instructions are collected from user
-# SELECTED_EVENTS is the list of enabled hook events
-# Build the JSON using jq
-
-# Example: session-start and session-end selected, bearer auth
-jq -n \
-  --arg gateway_url "$GATEWAY_URL" \
-  --arg auth_header "$AUTH_HEADER" \
-  --arg session_start_instruction "$SESSION_START_INSTRUCTION" \
-  --arg session_end_instruction "$SESSION_END_INSTRUCTION" \
-  --arg stop_instruction "$STOP_INSTRUCTION" \
-  '{
-    enabled: true,
-    gateways: {
-      "my-gateway": {
-        url: $gateway_url,
-        headers: (if $auth_header != "" then {"Authorization": $auth_header} else {} end),
-        method: "POST",
-        timeout: 10000
-      }
-    },
-    hooks: {
-      "session-start": {gateway: "my-gateway", instruction: $session_start_instruction, enabled: true},
-      "session-end": {gateway: "my-gateway", instruction: $session_end_instruction, enabled: true},
-      "stop": {gateway: "my-gateway", instruction: $stop_instruction, enabled: true}
-    }
-  }' > "$CONFIG_FILE"
-```
-
-Adjust the hooks object to include only the events the user selected, with their chosen instructions.
-
----
-
-## Step 7: Test the Gateway
-
-After writing config, offer to send a test wake call:
-
-Use AskUserQuestion:
-
-**Question:** "Send a test wake call to your gateway to verify the connection?"
-
-**Options:**
-1. **Yes, test now (Recommended)** - Send a test HTTP POST to the gateway
-2. **No, I'll test later** - Skip testing
-
-If testing:
-
-```bash
-GATEWAY_URL="USER_PROVIDED_URL"
-AUTH_HEADER="USER_PROVIDED_AUTH_HEADER"  # may be empty
-
-# Build auth header arg
-AUTH_ARG=""
-if [ -n "$AUTH_HEADER" ]; then
-  AUTH_ARG="-H \"Authorization: $AUTH_HEADER\""
-fi
-
-RESPONSE=$(eval curl -s -w "\n%{http_code}" \
-  -H "Content-Type: application/json" \
-  $AUTH_ARG \
-  -d '{"event":"session-start","instruction":"OpenClaw test wake from OMC configure wizard","timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","context":{}}' \
-  "$GATEWAY_URL")
-
-HTTP_CODE=$(echo "$RESPONSE" | tail -1)
-BODY=$(echo "$RESPONSE" | head -1)
-
-if [ "$HTTP_CODE" = "200" ] || [ "$HTTP_CODE" = "201" ] || [ "$HTTP_CODE" = "202" ] || [ "$HTTP_CODE" = "204" ]; then
-  echo "Test wake succeeded (HTTP $HTTP_CODE)!"
-else
-  echo "Test wake failed (HTTP $HTTP_CODE):"
-  echo "$BODY"
-fi
-```
-
-Report success or failure. Common issues:
-- **401 Unauthorized**: Auth header is missing or incorrect
-- **403 Forbidden**: Token does not have permission
-- **404 Not Found**: Gateway URL path is incorrect
-- **SSL error**: URL must be HTTPS with a valid certificate
-- **Connection refused**: Gateway is not running or URL is wrong
-
----
-
-## Step 8: Confirm
-
-Display the final configuration summary:
-
-```
-OpenClaw Gateway Configured!
-
-  Gateway:  https://my-gateway.example.com/wake
-  Auth:     Bearer *** (configured)
-  Events:   session-start, session-end, stop
-
-Config saved to: ~/.claude/omc_config.openclaw.json
-
-To activate OpenClaw, use one of:
-  omc --openclaw                  (per-session flag)
-  export OMC_OPENCLAW=1           (environment variable)
-
-Debug logging:
-  export OMC_OPENCLAW_DEBUG=1     (logs wake results to stderr)
-
-Custom config path:
-  export OMC_OPENCLAW_CONFIG=/path/to/config.json
-
-To reconfigure: /oh-my-claudecode:configure-openclaw
-```
-
----
-
-## Template Variables Reference
-
-| Event | Available Variables |
-|-------|-------------------|
-| `session-start` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{timestamp}}`, `{{event}}` |
-| `session-end` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{contextSummary}}`, `{{reason}}`, `{{timestamp}}`, `{{event}}` |
-| `pre-tool-use` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{toolName}}`, `{{timestamp}}`, `{{event}}` |
-| `post-tool-use` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{toolName}}`, `{{timestamp}}`, `{{event}}` |
-| `stop` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{timestamp}}`, `{{event}}` |
-| `keyword-detector` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{prompt}}`, `{{timestamp}}`, `{{event}}` |
-| `ask-user-question` | `{{sessionId}}`, `{{projectPath}}`, `{{projectName}}`, `{{question}}`, `{{timestamp}}`, `{{event}}` |
-
-Unresolved variables (e.g., `{{unknown}}`) are left as-is in the instruction text.
-
----
-
-## Environment Variable Alternative
-
-Users can skip this wizard entirely by setting env vars and writing the config manually:
-
-```bash
-# Enable OpenClaw
-export OMC_OPENCLAW=1
-
-# Optional: override config file path
-export OMC_OPENCLAW_CONFIG="$HOME/.claude/omc_config.openclaw.json"
-
-# Optional: enable debug logging
-export OMC_OPENCLAW_DEBUG=1
-```
-
-The config file path defaults to `~/.claude/omc_config.openclaw.json`. Use `OMC_OPENCLAW_CONFIG` to override.

package/skills/learn-about-omc/SKILL.md

@@ -1,37 +0,0 @@
----
-name: learn-about-omc
-description: Learn about your OMC usage patterns and get personalized recommendations
----
-
-# Learn About OMC
-
-Analyze your OMC usage patterns and provide personalized recommendations for getting more out of oh-my-claudecode.
-
-## Usage
-
-```
-/oh-my-claudecode:learn-about-omc
-```
-
-## Behavior
-
-1. **Scan usage data** from:
-   - `.omc/sessions/` for session history
-   - `.omc/state/` for mode usage patterns
-   - `.omc/notepad.md` for working memory
-   - `.omc/project-memory.json` for project context
-   - Agent flow traces for tool and agent usage
-2. **Analyze patterns**:
-   - Most-used modes and skills
-   - Agent types spawned most frequently
-   - Common workflows and task types
-   - Session durations and completion rates
-3. **Generate recommendations**:
-   - Underused features that match your workflow
-   - More efficient skill combinations
-   - Configuration optimizations
-   - Tips based on your usage profile
-
-## Output
-
-A personalized report with usage statistics and actionable recommendations for improving your OMC workflow.

package/skills/note/SKILL.md

@@ -1,62 +0,0 @@
----
-name: note
-description: Save notes to notepad.md for compaction resilience
----
-
-# Note Skill
-
-Save important context to `.omc/notepad.md` that survives conversation compaction.
-
-## Usage
-
-| Command | Action |
-|---------|--------|
-| `/oh-my-claudecode:note <content>` | Add to Working Memory with timestamp |
-| `/oh-my-claudecode:note --priority <content>` | Add to Priority Context (always loaded) |
-| `/oh-my-claudecode:note --manual <content>` | Add to MANUAL section (never pruned) |
-| `/oh-my-claudecode:note --show` | Display current notepad contents |
-| `/oh-my-claudecode:note --prune` | Remove entries older than 7 days |
-| `/oh-my-claudecode:note --clear` | Clear Working Memory (keep Priority + MANUAL) |
-
-## Sections
-
-### Priority Context (500 char limit)
-- **Always** injected on session start
-- Use for critical facts: "Project uses pnpm", "API in src/api/client.ts"
-- Keep it SHORT - this eats into your context budget
-
-### Working Memory
-- Timestamped session notes
-- Auto-pruned after 7 days
-- Good for: debugging breadcrumbs, temporary findings
-
-### MANUAL
-- Never auto-pruned
-- User-controlled permanent notes
-- Good for: team contacts, deployment info
-
-## Examples
-
-```
-/oh-my-claudecode:note Found auth bug in UserContext - missing useEffect dependency
-/oh-my-claudecode:note --priority Project uses TypeScript strict mode, all files in src/
-/oh-my-claudecode:note --manual Contact: api-team@company.com for backend questions
-/oh-my-claudecode:note --show
-/oh-my-claudecode:note --prune
-```
-
-## Behavior
-
-1. Creates `.omc/notepad.md` if it doesn't exist
-2. Parses the argument to determine section
-3. Appends content with timestamp (for Working Memory)
-4. Warns if Priority Context exceeds 500 chars
-5. Confirms what was saved
-
-## Integration
-
-Notepad content is automatically loaded on session start:
-- Priority Context: ALWAYS loaded
-- Working Memory: Loaded if recent entries exist
-
-This helps survive conversation compaction without losing critical context.

package/skills/omc-help/SKILL.md

@@ -1,192 +0,0 @@
----
-name: omc-help
-description: Guide on using oh-my-claudecode plugin
----
-
-# How OMC Works
-
-**You don't need to learn any commands!** OMC enhances Claude Code with intelligent behaviors that activate automatically.
-
-## What Happens Automatically
-
-| When You... | I Automatically... |
-|-------------|-------------------|
-| Give me a complex task | Parallelize and delegate to specialist agents |
-| Ask me to plan something | Start a planning interview |
-| Need something done completely | Persist until verified complete |
-| Work on UI/frontend | Activate design sensibility |
-| Say "stop" or "cancel" | Intelligently stop current operation |
-
-## Magic Keywords (Optional Shortcuts)
-
-You can include these words naturally in your request for explicit control:
-
-| Keyword | Effect | Example |
-|---------|--------|---------|
-| **ralph** | Persistence mode | "ralph: fix all the bugs" |
-| **ralplan** | Iterative planning | "ralplan this feature" |
-| **ulw** | Max parallelism | "ulw refactor the API" |
-| **plan** | Planning interview | "plan the new endpoints" |
-
-**ralph includes ultrawork:** When you activate ralph mode, it automatically includes ultrawork's parallel execution. No need to combine keywords.
-
-## Stopping Things
-
-Just say:
-- "stop"
-- "cancel"
-- "abort"
-
-I'll figure out what to stop based on context.
-
-## First Time Setup
-
-If you haven't configured OMC yet:
-
-```
-/oh-my-claudecode:omc-setup
-```
-
-This is the **only command** you need to know. It downloads the configuration and you're done.
-
-## For 2.x Users
-
-Your old commands still work! `/ralph`, `/ultrawork`, `/omc-plan`, etc. all function exactly as before.
-
-But now you don't NEED them - everything is automatic.
-
----
-
-## Usage Analysis
-
-Analyze your oh-my-claudecode usage and get tailored recommendations to improve your workflow.
-
-> Note: This replaces the former `/oh-my-claudecode:learn-about-omc` skill.
-
-### What It Does
-
-1. Reads token tracking from `~/.omc/state/token-tracking.jsonl`
-2. Reads session history from `.omc/state/session-history.json`
-3. Analyzes agent usage patterns
-4. Identifies underutilized features
-5. Recommends configuration changes
-
-### Step 1: Gather Data
-
-```bash
-# Check for token tracking data
-TOKEN_FILE="$HOME/.omc/state/token-tracking.jsonl"
-SESSION_FILE=".omc/state/session-history.json"
-CONFIG_FILE="$HOME/.claude/.omc-config.json"
-
-echo "Analyzing OMC Usage..."
-echo ""
-
-# Check what data is available
-HAS_TOKENS=false
-HAS_SESSIONS=false
-HAS_CONFIG=false
-
-if [[ -f "$TOKEN_FILE" ]]; then
-  HAS_TOKENS=true
-  TOKEN_COUNT=$(wc -l < "$TOKEN_FILE")
-  echo "Token records found: $TOKEN_COUNT"
-fi
-
-if [[ -f "$SESSION_FILE" ]]; then
-  HAS_SESSIONS=true
-  SESSION_COUNT=$(cat "$SESSION_FILE" | jq '.sessions | length' 2>/dev/null || echo "0")
-  echo "Sessions found: $SESSION_COUNT"
-fi
-
-if [[ -f "$CONFIG_FILE" ]]; then
-  HAS_CONFIG=true
-  DEFAULT_MODE=$(cat "$CONFIG_FILE" | jq -r '.defaultExecutionMode // "not set"')
-  echo "Default execution mode: $DEFAULT_MODE"
-fi
-```
-
-### Step 2: Analyze Agent Usage (if token data exists)
-
-```bash
-if [[ "$HAS_TOKENS" == "true" ]]; then
-  echo ""
-  echo "TOP AGENTS BY USAGE:"
-  cat "$TOKEN_FILE" | jq -r '.agentName // "main"' | sort | uniq -c | sort -rn | head -10
-
-  echo ""
-  echo "MODEL DISTRIBUTION:"
-  cat "$TOKEN_FILE" | jq -r '.modelName' | sort | uniq -c | sort -rn
-fi
-```
-
-### Step 3: Generate Recommendations
-
-Based on patterns found, output recommendations:
-
-**If high Opus usage (>40%) and no :**
-- "Consider using  for routine tasks to save tokens"
-
-**If no pipeline usage:**
-- "Try /pipeline for code review workflows"
-
-**If no security-reviewer usage:**
-- "Use security-reviewer after auth/API changes"
-
-**If defaultExecutionMode not set:**
-- "Set defaultExecutionMode in /omc-setup for consistent behavior"
-
-### Step 4: Output Report
-
-Format a summary with:
-- Token summary (total, by model)
-- Top agents used
-- Underutilized features
-- Personalized recommendations
-
-### Example Output
-
-```
-📊 Your OMC Usage Analysis
-
-TOKEN SUMMARY:
-- Total records: 1,234
-- By Model: opus 45%, sonnet 40%, haiku 15%
-
-TOP AGENTS:
-1. executor (234 uses)
-2. architect (89 uses)
-3. explore (67 uses)
-
-UNDERUTILIZED FEATURES:
-- : 0 uses (could save ~30% on routine tasks)
-- pipeline: 0 uses (great for review workflows)
-
-RECOMMENDATIONS:
-1. Set defaultExecutionMode: "" to save tokens
-2. Try /pipeline review for PR reviews
-3. Use explore agent before architect to save context
-```
-
-### Graceful Degradation
-
-If no data found:
-
-```
-📊 Limited Usage Data Available
-
-No token tracking found. To enable tracking:
-1. Ensure ~/.omc/state/ directory exists
-2. Run any OMC command to start tracking
-
-Tip: Run /omc-setup to configure OMC properly.
-```
-
-## Need More Help?
-
-- **README**: https://github.com/<your-owner>/oh-my-claudecode
-- **Issues**: https://github.com/<your-owner>/oh-my-claudecode/issues
-
----
-
-*Version: 4.2.3*