oh-my-codex 0.8.0 → 0.8.2

package/templates/AGENTS.md

@@ -149,6 +149,8 @@ Do not ask for confirmation — just read the skill file and follow its instruct
 | "ralph", "don't stop", "must complete", "keep going" | `$ralph` | Read `~/.agents/skills/ralph/SKILL.md`, execute persistence loop |
 | "autopilot", "build me", "I want a" | `$autopilot` | Read `~/.agents/skills/autopilot/SKILL.md`, execute autonomous pipeline |
 | "ultrawork", "ulw", "parallel" | `$ultrawork` | Read `~/.agents/skills/ultrawork/SKILL.md`, execute parallel agents |
+| "ultraqa" | `$ultraqa` | Read `~/.agents/skills/ultraqa/SKILL.md`, run QA cycling workflow |
+| "analyze", "investigate" | `$analyze` | Read `~/.agents/skills/analyze/SKILL.md`, run deep analysis |
 | "plan this", "plan the", "let's plan" | `$plan` | Read `~/.agents/skills/plan/SKILL.md`, start planning workflow |
 | "interview", "deep interview", "gather requirements", "interview me", "don't assume", "ouroboros" | `$deep-interview` | Read `~/.agents/skills/deep-interview/SKILL.md`, run Ouroboros-inspired Socratic ambiguity-gated interview workflow |
 | "ralplan", "consensus plan" | `$ralplan` | Read `~/.agents/skills/ralplan/SKILL.md`, start consensus planning with RALPLAN-DR structured deliberation (short by default, `--deliberate` for high-risk) |
@@ -157,14 +159,16 @@ Do not ask for confirmation — just read the skill file and follow its instruct
 | "cancel", "stop", "abort" | `$cancel` | Read `~/.agents/skills/cancel/SKILL.md`, cancel active modes |
 | "tdd", "test first" | `$tdd` | Read `~/.agents/skills/tdd/SKILL.md`, start test-driven workflow |
 | "fix build", "type errors" | `$build-fix` | Read `~/.agents/skills/build-fix/SKILL.md`, fix build errors |
-| "review code" | `$code-review` | Read `~/.agents/skills/code-review/SKILL.md`, run code review |
+| "review code", "code review", "code-review" | `$code-review` | Read `~/.agents/skills/code-review/SKILL.md`, run code review |
 | "security review" | `$security-review` | Read `~/.agents/skills/security-review/SKILL.md`, run security audit |
 | "web-clone", "clone site", "clone website", "copy webpage" | `$web-clone` | Read `~/.agents/skills/web-clone/SKILL.md`, start website cloning pipeline |
 
 Detection rules:
 - Keywords are case-insensitive and match anywhere in the user's message
-- If multiple keywords match, use the most specific (longest match)
-- Conflict resolution: explicit `$name` invocation overrides keyword detection
+- If one or more explicit `$name` tokens are present, execute **all explicit skills left-to-right**.
+- If multiple non-explicit keywords match, use the most specific (longest match).
+- Conflict resolution: explicit `$name` invocation overrides keyword detection.
+- If user explicitly invokes `/prompts:<name>`, treat it as direct prompt execution and do not auto-activate keyword skills unless explicit `$name` tokens are also present.
 - The rest of the user's message (after keyword extraction) becomes the task description
 
 Ralph / Ralplan execution gate:

package/templates/catalog-manifest.json

@@ -234,19 +234,42 @@
       "core": false,
       "internalRequired": false
     },
+    {
+      "name": "configure-notifications",
+      "category": "utility",
+      "status": "active",
+      "core": false,
+      "internalRequired": false
+    },
+    {
+      "name": "configure-discord",
+      "category": "utility",
+      "status": "merged",
+      "canonical": "configure-notifications",
+      "core": false,
+      "internalRequired": false
+    },
     {
       "name": "configure-telegram",
       "category": "utility",
       "status": "merged",
-      "canonical": "omx-setup",
+      "canonical": "configure-notifications",
       "core": false,
       "internalRequired": false
     },
     {
-      "name": "configure-discord",
+      "name": "configure-slack",
+      "category": "utility",
+      "status": "merged",
+      "canonical": "configure-notifications",
+      "core": false,
+      "internalRequired": false
+    },
+    {
+      "name": "configure-openclaw",
       "category": "utility",
       "status": "merged",
-      "canonical": "omx-setup",
+      "canonical": "configure-notifications",
       "core": false,
       "internalRequired": false
     },

package/skills/configure-discord/SKILL.md

@@ -1,256 +0,0 @@
----
-name: configure-discord
-description: Configure Discord webhook/bot notifications via natural language
-triggers:
-  - "configure discord"
-  - "setup discord"
-  - "discord notifications"
-  - "discord webhook"
----
-
-# Configure Discord Notifications
-
-Set up Discord notifications so OMX can ping you when sessions end, need input, or complete background tasks.
-
-## 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 `~/.codex/.omx-config.json`.
-
-## Step 1: Detect Existing Configuration
-
-```bash
-CONFIG_FILE="$HOME/.codex/.omx-config.json"
-
-if [ -f "$CONFIG_FILE" ]; then
-  # Check for existing discord config
-  HAS_DISCORD=$(jq -r '.notifications.discord.enabled // false' "$CONFIG_FILE" 2>/dev/null)
-  HAS_DISCORD_BOT=$(jq -r '.notifications["discord-bot"].enabled // false' "$CONFIG_FILE" 2>/dev/null)
-  WEBHOOK_URL=$(jq -r '.notifications.discord.webhookUrl // empty' "$CONFIG_FILE" 2>/dev/null)
-  MENTION=$(jq -r '.notifications.discord.mention // empty' "$CONFIG_FILE" 2>/dev/null)
-
-  if [ "$HAS_DISCORD" = "true" ] || [ "$HAS_DISCORD_BOT" = "true" ]; then
-    echo "EXISTING_CONFIG=true"
-    echo "WEBHOOK_CONFIGURED=$HAS_DISCORD"
-    echo "BOT_CONFIGURED=$HAS_DISCORD_BOT"
-    [ -n "$WEBHOOK_URL" ] && echo "WEBHOOK_URL=$WEBHOOK_URL"
-    [ -n "$MENTION" ] && echo "MENTION=$MENTION"
-  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: Choose Discord Method
-
-Use AskUserQuestion:
-
-**Question:** "How would you like to send Discord notifications?"
-
-**Options:**
-1. **Webhook (Recommended)** - Create a webhook in your Discord channel. Simple, no bot needed. Just paste the URL.
-2. **Bot API** - Use a Discord bot token + channel ID. More flexible, requires a bot application.
-
-## Step 3A: Webhook Setup
-
-If user chose Webhook:
-
-Use AskUserQuestion:
-
-**Question:** "Paste your Discord webhook URL. To create one: Server Settings > Integrations > Webhooks > New Webhook > Copy URL"
-
-The user will type their webhook URL in the "Other" field.
-
-**Validate** the URL:
-- Must start with `https://discord.com/api/webhooks/` or `https://discordapp.com/api/webhooks/`
-- If invalid, explain the format and ask again
-
-## Step 3B: Bot API Setup
-
-If user chose Bot API:
-
-Ask two questions:
-
-1. **"Paste your Discord bot token"** - From discord.com/developers > Your App > Bot > Token
-2. **"Paste the channel ID"** - Right-click channel > Copy Channel ID (requires Developer Mode)
-
-## Step 4: Configure Mention (User Ping)
-
-Use AskUserQuestion:
-
-**Question:** "Would you like notifications to mention (ping) someone?"
-
-**Options:**
-1. **Yes, mention a user** - Tag a specific user by their Discord user ID
-2. **Yes, mention a role** - Tag a role by its role ID
-3. **No mentions** - Just post the message without pinging anyone
-
-### If user wants to mention a user:
-
-Ask: "What is the Discord user ID to mention? (Right-click user > Copy User ID, requires Developer Mode)"
-
-The mention format is: `<@USER_ID>` (e.g., `<@1465264645320474637>`)
-
-### If user wants to mention a role:
-
-Ask: "What is the Discord role ID to mention? (Server Settings > Roles > right-click role > Copy Role ID)"
-
-The mention format is: `<@&ROLE_ID>` (e.g., `<@&123456789>`)
-
-## Step 5: Configure Events
-
-Use AskUserQuestion with multiSelect:
-
-**Question:** "Which events should trigger Discord notifications?"
-
-**Options (multiSelect: true):**
-1. **Session end (Recommended)** - When a Codex session finishes
-2. **Input needed** - When Codex is waiting for your response (great for long-running tasks)
-3. **Session start** - When a new session begins
-4. **Session continuing** - When a persistent mode keeps the session alive
-
-Default selection: session-end + ask-user-question.
-
-## Step 6: Optional Username Override
-
-Use AskUserQuestion:
-
-**Question:** "Custom bot display name? (Shows as the webhook sender name in Discord)"
-
-**Options:**
-1. **OMX (default)** - Display as "OMX"
-2. **Codex CLI** - Display as "Codex CLI"
-3. **Custom** - Enter a custom name
-
-## Step 7: Write Configuration
-
-Read the existing config, merge the new Discord settings, and write back:
-
-```bash
-CONFIG_FILE="$HOME/.codex/.omx-config.json"
-mkdir -p "$(dirname "$CONFIG_FILE")"
-
-if [ -f "$CONFIG_FILE" ]; then
-  EXISTING=$(cat "$CONFIG_FILE")
-else
-  EXISTING='{}'
-fi
-```
-
-### For Webhook method:
-
-Build the notifications object with the collected values and merge into `.omx-config.json` using jq:
-
-```bash
-# WEBHOOK_URL, MENTION, USERNAME are collected from user
-# EVENTS is the list of enabled events
-
-echo "$EXISTING" | jq \
-  --arg url "$WEBHOOK_URL" \
-  --arg mention "$MENTION" \
-  --arg username "$USERNAME" \
-  '.notifications = (.notifications // {enabled: true}) |
-   .notifications.enabled = true |
-   .notifications.discord = {
-     enabled: true,
-     webhookUrl: $url,
-     mention: (if $mention == "" then null else $mention end),
-     username: (if $username == "" then null else $username end)
-   }' > "$CONFIG_FILE"
-```
-
-### For Bot API method:
-
-```bash
-echo "$EXISTING" | jq \
-  --arg token "$BOT_TOKEN" \
-  --arg channel "$CHANNEL_ID" \
-  --arg mention "$MENTION" \
-  '.notifications = (.notifications // {enabled: true}) |
-   .notifications.enabled = true |
-   .notifications["discord-bot"] = {
-     enabled: true,
-     botToken: $token,
-     channelId: $channel,
-     mention: (if $mention == "" then null else $mention end)
-   }' > "$CONFIG_FILE"
-```
-
-### Add event-specific config if user didn't select all events:
-
-For each event NOT selected, disable it:
-
-```bash
-# Example: disable session-start if not selected
-echo "$(cat "$CONFIG_FILE")" | jq \
-  '.notifications.events = (.notifications.events // {}) |
-   .notifications.events["session-start"] = {enabled: false}' > "$CONFIG_FILE"
-```
-
-## Step 8: Test the Configuration
-
-After writing config, offer to send a test notification:
-
-Use AskUserQuestion:
-
-**Question:** "Send a test notification to verify the setup?"
-
-**Options:**
-1. **Yes, test now (Recommended)** - Send a test message to your Discord channel
-2. **No, I'll test later** - Skip testing
-
-### If testing:
-
-```bash
-# For webhook:
-curl -s -o /dev/null -w "%{http_code}" \
-  -H "Content-Type: application/json" \
-  -d "{\"content\": \"${MENTION:+$MENTION\\n}OMX test notification - Discord is configured!\"}" \
-  "$WEBHOOK_URL"
-```
-
-Report success or failure. If it fails, help the user debug (check URL, permissions, etc.).
-
-## Step 9: Confirm
-
-Display the final configuration summary:
-
-```
-Discord Notifications Configured!
-
-  Method:   Webhook / Bot API
-  Mention:  <@1465264645320474637> (or "none")
-  Events:   session-end, ask-user-question
-  Username: OMX
-
-Config saved to: ~/.codex/.omx-config.json
-
-You can also set these via environment variables:
-  OMX_DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...
-  OMX_DISCORD_MENTION=<@1465264645320474637>
-
-To reconfigure: /configure-discord
-To configure Telegram: /configure-telegram
-```
-
-## Environment Variable Alternative
-
-Users can skip this wizard entirely by setting env vars in their shell profile:
-
-**Webhook method:**
-```bash
-export OMX_DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
-export OMX_DISCORD_MENTION="<@1465264645320474637>"  # optional
-```
-
-**Bot API method:**
-```bash
-export OMX_DISCORD_NOTIFIER_BOT_TOKEN="your-bot-token"
-export OMX_DISCORD_NOTIFIER_CHANNEL="your-channel-id"
-export OMX_DISCORD_MENTION="<@1465264645320474637>"  # optional
-```
-
-Env vars are auto-detected by the notification system without needing `.omx-config.json`.

package/skills/configure-openclaw/SKILL.md

@@ -1,264 +0,0 @@
----
-name: configure-openclaw
-description: Configure OpenClaw notification gateway via natural language
-triggers:
-  - "configure openclaw"
-  - "setup openclaw"
-  - "openclaw notifications"
-  - "openclaw gateway"
----
-
-# Configure OpenClaw Notifications
-
-Set up OpenClaw as a notification gateway so OMX can route notification events to your OpenClaw hook endpoints (or a local command gateway).
-
-## Runtime Schema Requirement (must match OMX)
-
-Always write OpenClaw config under:
-- `notifications.openclaw.enabled`
-- `notifications.openclaw.gateways`
-- `notifications.openclaw.hooks`
-
-Do **not** use legacy keys like `gatewayType`, `endpoint`, or top-level `command`.
-
-## How This Skill Works
-
-This is an interactive setup wizard. Ask questions with AskUserQuestion, merge changes into `~/.codex/.omx-config.json`, and then run a verification flow with explicit pass/fail diagnostics.
-
-## Step 1: Detect Existing OpenClaw Configuration
-
-```bash
-CONFIG_FILE="$HOME/.codex/.omx-config.json"
-
-if [ -f "$CONFIG_FILE" ]; then
-  OPENCLAW_ENABLED=$(jq -r '.notifications.openclaw.enabled // false' "$CONFIG_FILE" 2>/dev/null)
-  GATEWAYS=$(jq -r '.notifications.openclaw.gateways // {} | keys | join(", ")' "$CONFIG_FILE" 2>/dev/null)
-  HOOKS=$(jq -r '.notifications.openclaw.hooks // {} | keys | join(", ")' "$CONFIG_FILE" 2>/dev/null)
-
-  echo "OPENCLAW_ENABLED=$OPENCLAW_ENABLED"
-  echo "GATEWAYS=${GATEWAYS:-none}"
-  echo "HOOKS=${HOOKS:-none}"
-else
-  echo "NO_CONFIG_FILE"
-fi
-```
-
-If existing config is found, show current gateways/hooks and ask whether to update or replace.
-
-## Step 2: Choose Gateway Mode
-
-Use AskUserQuestion:
-
-**Question:** "Which OpenClaw gateway mode do you want to configure?"
-
-**Options:**
-1. **HTTP Gateway (Recommended)** - OMX POSTs JSON to your OpenClaw hook endpoint
-2. **CLI Command Gateway** - OMX executes a local command template
-
-## Step 3A: HTTP Gateway Setup
-
-Collect three values:
-1. Gateway name (default: `local`)
-2. Hook base URL (example: `http://127.0.0.1:18789`)
-3. OpenClaw hooks token
-
-Build the endpoint URL as:
-- Delivery endpoint: `${BASE_URL%/}/hooks/agent`
-- Optional wake smoke endpoint: `${BASE_URL%/}/hooks/wake`
-
-### Required validation checks
-
-Run these checks and report each result:
-
-1) **Hook token present**
-```bash
-[ -n "$HOOKS_TOKEN" ] && echo "PASS token provided" || echo "FAIL token missing"
-```
-
-2) **Gateway URL format and reachability**
-```bash
-case "$BASE_URL" in
-  http://*|https://*) echo "PASS URL format" ;;
-  *) echo "FAIL URL must start with http:// or https://" ;;
-esac
-
-curl -sS -o /dev/null -w "HTTP %{http_code}\n" "$BASE_URL" || echo "FAIL cannot reach base URL"
-```
-
-3) **Delivery endpoint probe (`/hooks/agent`)**
-```bash
-curl -sS -o /tmp/omx-openclaw-agent.json -w "HTTP %{http_code}\n" \
-  -X POST "${BASE_URL%/}/hooks/agent" \
-  -H "Authorization: Bearer $HOOKS_TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"instruction":"OMX OpenClaw setup probe","event":"session-end","sessionId":"setup-smoke"}'
-```
-
-If probe is non-2xx or network fails, treat as setup failure and continue with diagnostics.
-
-## Step 3B: CLI Command Gateway Setup
-
-Collect:
-- Gateway name (default: `local-command`)
-- Command template (supports `{{event}}`, `{{instruction}}`, `{{sessionId}}`, `{{projectPath}}`)
-
-Example:
-```bash
-~/.local/bin/my-notifier --event {{event}} --text {{instruction}}
-```
-
-### Dual env gate (must be explained)
-
-CLI command gateways only run when **both** are set:
-
-```bash
-export OMX_OPENCLAW=1
-export OMX_OPENCLAW_COMMAND=1
-```
-
-If `OMX_OPENCLAW_COMMAND` is missing, command gateway dispatch is blocked by design.
-
-## Step 4: Select Hook Event Mappings
-
-Use AskUserQuestion with multiSelect.
-
-**Question:** "Which OMX events should trigger OpenClaw hooks?"
-
-Recommended defaults:
-- `session-end`
-- `ask-user-question`
-
-Optional:
-- `session-start`
-- `session-idle`
-- `stop`
-
-For each selected event, collect a short instruction template.
-
-## Step 5: Write Schema-Aligned Config
-
-Always merge into `~/.codex/.omx-config.json`.
-
-### HTTP gateway example
-
-```bash
-jq \
-  --arg gatewayName "$GATEWAY_NAME" \
-  --arg url "${BASE_URL%/}/hooks/agent" \
-  --arg token "$HOOKS_TOKEN" \
-  '.notifications = (.notifications // {enabled: true}) |
-   .notifications.enabled = true |
-   .notifications.openclaw = (.notifications.openclaw // {}) |
-   .notifications.openclaw.enabled = true |
-   .notifications.openclaw.gateways = (.notifications.openclaw.gateways // {}) |
-   .notifications.openclaw.gateways[$gatewayName] = {
-     type: "http",
-     url: $url,
-     headers: {"Authorization": ("Bearer " + $token)}
-   }' "$CONFIG_FILE" > "$CONFIG_FILE.tmp" && mv "$CONFIG_FILE.tmp" "$CONFIG_FILE"
-```
-
-### Command gateway example
-
-```bash
-jq \
-  --arg gatewayName "$GATEWAY_NAME" \
-  --arg command "$COMMAND_TEMPLATE" \
-  '.notifications = (.notifications // {enabled: true}) |
-   .notifications.enabled = true |
-   .notifications.openclaw = (.notifications.openclaw // {}) |
-   .notifications.openclaw.enabled = true |
-   .notifications.openclaw.gateways = (.notifications.openclaw.gateways // {}) |
-   .notifications.openclaw.gateways[$gatewayName] = {
-     type: "command",
-     command: $command
-   }' "$CONFIG_FILE" > "$CONFIG_FILE.tmp" && mv "$CONFIG_FILE.tmp" "$CONFIG_FILE"
-```
-
-### Hook mapping example
-
-```bash
-jq \
-  --arg gatewayName "$GATEWAY_NAME" \
-  '.notifications.openclaw.hooks = (.notifications.openclaw.hooks // {}) |
-   .notifications.openclaw.hooks["session-end"] = {
-     enabled: true,
-     gateway: $gatewayName,
-     instruction: "OMX task completed for {{projectPath}}"
-   } |
-   .notifications.openclaw.hooks["ask-user-question"] = {
-     enabled: true,
-     gateway: $gatewayName,
-     instruction: "OMX needs input: {{question}}"
-   }' "$CONFIG_FILE" > "$CONFIG_FILE.tmp" && mv "$CONFIG_FILE.tmp" "$CONFIG_FILE"
-```
-
-## Step 6: Explain Activation Gates
-
-Show this exactly:
-
-```bash
-# Required for OpenClaw integration
-export OMX_OPENCLAW=1
-
-# Required in addition for command gateways
-export OMX_OPENCLAW_COMMAND=1
-```
-
-## Step 7: Verification Flow (required)
-
-Run both checks for HTTP gateways:
-
-### A) Wake smoke test (`/hooks/wake`)
-
-```bash
-curl -sS -X POST "${BASE_URL%/}/hooks/wake" \
-  -H "Authorization: Bearer $HOOKS_TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"text":"OMX wake smoke test","mode":"now"}'
-```
-
-Expected pass signal: JSON includes `"ok":true`.
-
-### B) Delivery verification (`/hooks/agent`) — not wake-only
-
-```bash
-curl -sS -o /tmp/omx-openclaw-delivery.json -w "HTTP %{http_code}\n" \
-  -X POST "${BASE_URL%/}/hooks/agent" \
-  -H "Authorization: Bearer $HOOKS_TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"instruction":"OMX delivery verification","event":"session-end","sessionId":"verify-setup"}'
-```
-
-Expected pass signal: HTTP 2xx and response body confirms acceptance.
-
-## Step 8: Pass/Fail Diagnostics Guidance
-
-If verification fails, guide with this checklist:
-- **401/403** → token missing/invalid; rotate token and update `Authorization` header.
-- **404** → wrong path; verify `/hooks/agent` and `/hooks/wake` are enabled by OpenClaw hooks config.
-- **5xx** → OpenClaw gateway runtime issue; check gateway logs and retry.
-- **Timeout / connection refused** → gateway URL unreachable; confirm host/port and local firewall.
-- **Command gateway disabled** → set both `OMX_OPENCLAW=1` and `OMX_OPENCLAW_COMMAND=1`.
-
-## Step 9: Final Summary
-
-Show:
-- gateway mode + gateway name
-- mapped events
-- whether smoke test passed
-- whether `/hooks/agent` delivery test passed
-- exact env vars user still needs to export in shell profile
-
-## Environment Variable Reference
-
-```bash
-# Required for all OpenClaw gateways
-export OMX_OPENCLAW=1
-
-# Required additionally for CLI command gateways
-export OMX_OPENCLAW_COMMAND=1
-
-# Optional debug logs
-export OMX_OPENCLAW_DEBUG=1
-```