claudecode-omc 4.3.4

package/skills/omc-doctor/SKILL.md

@@ -0,0 +1,188 @@
+---
+name: omc-doctor
+description: Diagnose and fix oh-my-claudecode installation issues
+---
+
+# Doctor Skill
+
+Note: All `~/.claude/...` paths in this guide respect `CLAUDE_CONFIG_DIR` when that environment variable is set.
+
+## Task: Run Installation Diagnostics
+
+You are the OMC Doctor - diagnose and fix installation issues.
+
+### Step 1: Check Plugin Version
+
+```bash
+# Get installed and latest versions (cross-platform)
+node -e "const p=require('path'),f=require('fs'),h=require('os').homedir(),d=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude'),b=p.join(d,'plugins','cache','omc','oh-my-claudecode');try{const v=f.readdirSync(b).filter(x=>/^\d/.test(x)).sort((a,c)=>a.localeCompare(c,void 0,{numeric:true}));console.log('Installed:',v.length?v[v.length-1]:'(none)')}catch{console.log('Installed: (none)')}"
+npm view oh-my-claudecode version 2>/dev/null || echo "Latest: (unavailable)"
+```
+
+**Diagnosis**:
+- If no version installed: CRITICAL - plugin not installed
+- If INSTALLED != LATEST: WARN - outdated plugin
+- If multiple versions exist: WARN - stale cache
+
+### Step 2: Check for Legacy Hooks in settings.json
+
+Read both `~/.claude/settings.json` (profile-level) and `./.claude/settings.json` (project-level) and check if there's a `"hooks"` key with entries like:
+- `bash $HOME/.claude/hooks/keyword-detector.sh`
+- `bash $HOME/.claude/hooks/persistent-mode.sh`
+- `bash $HOME/.claude/hooks/session-start.sh`
+
+**Diagnosis**:
+- If found: CRITICAL - legacy hooks causing duplicates
+
+### Step 3: Check for Legacy Bash Hook Scripts
+
+```bash
+ls -la ~/.claude/hooks/*.sh 2>/dev/null
+```
+
+**Diagnosis**:
+- If `keyword-detector.sh`, `persistent-mode.sh`, `session-start.sh`, or `stop-continuation.sh` exist: WARN - legacy scripts (can cause confusion)
+
+### Step 4: Check CLAUDE.md
+
+```bash
+# Check if CLAUDE.md exists
+ls -la ~/.claude/CLAUDE.md 2>/dev/null
+
+# Check for OMC marker
+grep -q "oh-my-claudecode Multi-Agent System" ~/.claude/CLAUDE.md 2>/dev/null && echo "Has OMC config" || echo "Missing OMC config"
+```
+
+**Diagnosis**:
+- If missing: CRITICAL - CLAUDE.md not configured
+- If missing OMC marker: WARN - outdated CLAUDE.md
+
+### Step 5: Check for Stale Plugin Cache
+
+```bash
+# Count versions in cache (cross-platform)
+node -e "const p=require('path'),f=require('fs'),h=require('os').homedir(),d=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude'),b=p.join(d,'plugins','cache','omc','oh-my-claudecode');try{const v=f.readdirSync(b).filter(x=>/^\d/.test(x));console.log(v.length+' version(s):',v.join(', '))}catch{console.log('0 versions')}"
+```
+
+**Diagnosis**:
+- If > 1 version: WARN - multiple cached versions (cleanup recommended)
+
+### Step 6: Check for Legacy Curl-Installed Content
+
+Check for legacy agents, commands, and skills installed via curl (before plugin system):
+
+```bash
+# Check for legacy agents directory
+ls -la ~/.claude/agents/ 2>/dev/null
+
+# Check for legacy commands directory
+ls -la ~/.claude/commands/ 2>/dev/null
+
+# Check for legacy skills directory
+ls -la ~/.claude/skills/ 2>/dev/null
+```
+
+**Diagnosis**:
+- If `~/.claude/agents/` exists with oh-my-claudecode-related files: WARN - legacy agents (now provided by plugin)
+- If `~/.claude/commands/` exists with oh-my-claudecode-related files: WARN - legacy commands (now provided by plugin)
+- If `~/.claude/skills/` exists with oh-my-claudecode-related files: WARN - legacy skills (now provided by plugin)
+
+Look for files like:
+- `architect.md`, `document-specialist.md`, `explore.md`, `executor.md`, etc. in agents/
+- `ultrawork.md`, `deepsearch.md`, etc. in commands/
+- Any oh-my-claudecode-related `.md` files in skills/
+
+---
+
+## Report Format
+
+After running all checks, output a report:
+
+```
+## OMC Doctor Report
+
+### Summary
+[HEALTHY / ISSUES FOUND]
+
+### Checks
+
+| Check | Status | Details |
+|-------|--------|---------|
+| Plugin Version | OK/WARN/CRITICAL | ... |
+| Legacy Hooks (settings.json) | OK/CRITICAL | ... |
+| Legacy Scripts (~/.claude/hooks/) | OK/WARN | ... |
+| CLAUDE.md | OK/WARN/CRITICAL | ... |
+| Plugin Cache | OK/WARN | ... |
+| Legacy Agents (~/.claude/agents/) | OK/WARN | ... |
+| Legacy Commands (~/.claude/commands/) | OK/WARN | ... |
+| Legacy Skills (~/.claude/skills/) | OK/WARN | ... |
+
+### Issues Found
+1. [Issue description]
+2. [Issue description]
+
+### Recommended Fixes
+[List fixes based on issues]
+```
+
+---
+
+## Auto-Fix (if user confirms)
+
+If issues found, ask user: "Would you like me to fix these issues automatically?"
+
+If yes, apply fixes:
+
+### Fix: Legacy Hooks in settings.json
+Remove the `"hooks"` section from `~/.claude/settings.json` (keep other settings intact)
+
+### Fix: Legacy Bash Scripts
+```bash
+rm -f ~/.claude/hooks/keyword-detector.sh
+rm -f ~/.claude/hooks/persistent-mode.sh
+rm -f ~/.claude/hooks/session-start.sh
+rm -f ~/.claude/hooks/stop-continuation.sh
+```
+
+### Fix: Outdated Plugin
+```bash
+# Clear plugin cache (cross-platform)
+node -e "const p=require('path'),f=require('fs'),d=process.env.CLAUDE_CONFIG_DIR||p.join(require('os').homedir(),'.claude'),b=p.join(d,'plugins','cache','omc','oh-my-claudecode');try{f.rmSync(b,{recursive:true,force:true});console.log('Plugin cache cleared. Restart Claude Code to fetch latest version.')}catch{console.log('No plugin cache found')}"
+```
+
+### Fix: Stale Cache (multiple versions)
+```bash
+# Keep only latest version (cross-platform)
+node -e "const p=require('path'),f=require('fs'),h=require('os').homedir(),d=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude'),b=p.join(d,'plugins','cache','omc','oh-my-claudecode');try{const v=f.readdirSync(b).filter(x=>/^\d/.test(x)).sort((a,c)=>a.localeCompare(c,void 0,{numeric:true}));v.slice(0,-1).forEach(x=>f.rmSync(p.join(b,x),{recursive:true,force:true}));console.log('Removed',v.length-1,'old version(s)')}catch(e){console.log('No cache to clean')}"
+```
+
+### Fix: Missing/Outdated CLAUDE.md
+Fetch latest from GitHub and write to `~/.claude/CLAUDE.md`:
+```
+WebFetch(url: "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md", prompt: "Return the complete raw markdown content exactly as-is")
+```
+
+### Fix: Legacy Curl-Installed Content
+
+Remove legacy agents, commands, and skills directories (now provided by plugin):
+
+```bash
+# Backup first (optional - ask user)
+# mv ~/.claude/agents ~/.claude/agents.bak
+# mv ~/.claude/commands ~/.claude/commands.bak
+# mv ~/.claude/skills ~/.claude/skills.bak
+
+# Or remove directly
+rm -rf ~/.claude/agents
+rm -rf ~/.claude/commands
+rm -rf ~/.claude/skills
+```
+
+**Note**: Only remove if these contain oh-my-claudecode-related files. If user has custom agents/commands/skills, warn them and ask before removing.
+
+---
+
+## Post-Fix
+
+After applying fixes, inform user:
+> Fixes applied. **Restart Claude Code** for changes to take effect.

package/skills/omc-doctor/skill-debugger.md

@@ -0,0 +1,101 @@
+---
+description: Debug why a Claude Code skill isn't triggering when expected
+---
+
+# Skill Debugger
+
+[SKILL DEBUG MODE ACTIVATED]
+
+## Objective
+
+Systematically diagnose why a skill isn't triggering as expected. Identify root causes and provide actionable fixes.
+
+## Debugging Workflow
+
+### Step 1: Identify Target Skill
+
+Ask the user which skill isn't working, or infer from context. Then verify it exists:
+
+```bash
+# Check plugin skills
+ls ~/.claude/plugins/cache/omc/oh-my-claudecode/*/skills/<skill-name>/ 2>/dev/null
+
+# Check global skills
+ls ~/.claude/skills/<skill-name>/ 2>/dev/null
+```
+
+### Step 2: Validate SKILL.md
+
+Use the `Read` tool to read the target skill's `SKILL.md` and check:
+
+- [ ] File exists and is readable
+- [ ] YAML frontmatter has `---` delimiters
+- [ ] `name:` field matches folder name
+- [ ] `description:` is 50-150 characters, specific, not vague
+- [ ] No vague words ("helps", "assists", "various")
+
+### Step 3: Analyze Description Quality
+
+Compare the skill description against what the user asked. Check:
+
+- Does the description contain keywords the user would naturally say?
+- Is there a `<Use_When>` or "When to Use" section?
+- Are there at least 3 usage examples?
+
+### Step 4: Check for Conflicts
+
+Scan all installed skills for overlapping descriptions:
+
+```bash
+# List all skill descriptions
+for dir in ~/.claude/plugins/cache/omc/oh-my-claudecode/*/skills/*/; do
+  if [ -f "$dir/SKILL.md" ]; then
+    echo "=== $(basename $dir) ==="
+    head -5 "$dir/SKILL.md"
+    echo
+  fi
+done
+```
+
+Look for skills with similar keywords or overlapping use cases.
+
+### Step 5: Check Command Registration
+
+Verify if the skill has a corresponding slash command:
+
+```bash
+ls ~/.claude/plugins/cache/omc/oh-my-claudecode/*/commands/<skill-name>.md 2>/dev/null
+```
+
+If no command exists, the skill relies purely on semantic matching.
+
+## Diagnosis Report Format
+
+```
+## Skill Debug Report
+
+Skill: <name>
+Path: <location>
+Status: OK / NOT TRIGGERING / CONFLICT
+
+### Issues Found
+| Priority | Issue | Fix |
+|----------|-------|-----|
+| CRITICAL | ... | ... |
+| HIGH | ... | ... |
+| MEDIUM | ... | ... |
+
+### Recommendations
+1. [Specific fix with before/after examples]
+2. [...]
+```
+
+## Common Fixes
+
+| Problem | Fix |
+|---------|-----|
+| Description too vague | Add specific keywords and use cases |
+| No trigger keywords | Add words users would naturally say |
+| Wrong skill triggers | Differentiate descriptions between conflicting skills |
+| Skill not found | Check installation path and folder name |
+| No slash command | Create `commands/<name>.md` for explicit triggering |

package/skills/omc-help/SKILL.md

@@ -0,0 +1,192 @@
+---
+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`, `/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/Yeachan-Heo/oh-my-claudecode
+- **Issues**: https://github.com/Yeachan-Heo/oh-my-claudecode/issues
+
+---
+
+*Version: 4.2.3*