claudecode-omc 4.3.4

package/skills/configure-notifications/SKILL.md

@@ -0,0 +1,760 @@
+---
+name: configure-notifications
+description: Configure notification integrations (Telegram, Discord, Slack) via natural language
+triggers:
+  - "configure notifications"
+  - "setup notifications"
+  - "configure telegram"
+  - "setup telegram"
+  - "telegram bot"
+  - "configure discord"
+  - "setup discord"
+  - "discord webhook"
+  - "configure slack"
+  - "setup slack"
+  - "slack webhook"
+---
+
+# Configure Notifications
+
+Set up OMC notification integrations so you're alerted when sessions end, need input, or complete background tasks.
+
+## Routing
+
+Detect which provider the user wants based on their request or argument:
+- If the trigger or argument contains "telegram" → follow the **Telegram** section
+- If the trigger or argument contains "discord" → follow the **Discord** section
+- If the trigger or argument contains "slack" → follow the **Slack** section
+- If no provider is specified, use AskUserQuestion:
+
+**Question:** "Which notification service would you like to configure?"
+
+**Options:**
+1. **Telegram** - Bot token + chat ID. Works on mobile and desktop.
+2. **Discord** - Webhook or bot token + channel ID.
+3. **Slack** - Incoming webhook URL.
+
+---
+
+## Telegram Setup
+
+Set up Telegram notifications so OMC can message 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 `~/.claude/.omc-config.json`.
+
+### Step 1: Detect Existing Configuration
+
+```bash
+CONFIG_FILE="$HOME/.claude/.omc-config.json"
+
+if [ -f "$CONFIG_FILE" ]; then
+  HAS_TELEGRAM=$(jq -r '.notifications.telegram.enabled // false' "$CONFIG_FILE" 2>/dev/null)
+  CHAT_ID=$(jq -r '.notifications.telegram.chatId // empty' "$CONFIG_FILE" 2>/dev/null)
+  PARSE_MODE=$(jq -r '.notifications.telegram.parseMode // "Markdown"' "$CONFIG_FILE" 2>/dev/null)
+
+  if [ "$HAS_TELEGRAM" = "true" ]; then
+    echo "EXISTING_CONFIG=true"
+    echo "CHAT_ID=$CHAT_ID"
+    echo "PARSE_MODE=$PARSE_MODE"
+  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: Create a Telegram Bot
+
+Guide the user through creating a bot if they don't have one:
+
+```
+To set up Telegram notifications, you need a Telegram bot token and your chat ID.
+
+CREATE A BOT (if you don't have one):
+1. Open Telegram and search for @BotFather
+2. Send /newbot
+3. Choose a name (e.g., "My OMC Notifier")
+4. Choose a username (e.g., "my_omc_bot")
+5. BotFather will give you a token like: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz
+
+GET YOUR CHAT ID:
+1. Start a chat with your new bot (send /start)
+2. Visit: https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates
+3. Look for "chat":{"id":YOUR_CHAT_ID}
+   - Personal chat IDs are positive numbers (e.g., 123456789)
+   - Group chat IDs are negative numbers (e.g., -1001234567890)
+```
+
+### Step 3: Collect Bot Token
+
+Use AskUserQuestion:
+
+**Question:** "Paste your Telegram bot token (from @BotFather)"
+
+The user will type their token in the "Other" field.
+
+**Validate** the token:
+- Must match pattern: `digits:alphanumeric` (e.g., `123456789:ABCdefGHI...`)
+- If invalid, explain the format and ask again
+
+### Step 4: Collect Chat ID
+
+Use AskUserQuestion:
+
+**Question:** "Paste your Telegram chat ID (the number from getUpdates API)"
+
+The user will type their chat ID in the "Other" field.
+
+**Validate** the chat ID:
+- Must be a number (positive for personal, negative for groups)
+- If invalid, offer to help them find it:
+
+```bash
+# Help user find their chat ID
+BOT_TOKEN="USER_PROVIDED_TOKEN"
+echo "Fetching recent messages to find your chat ID..."
+curl -s "https://api.telegram.org/bot${BOT_TOKEN}/getUpdates" | jq '.result[-1].message.chat.id // .result[-1].message.from.id // "No messages found - send /start to your bot first"'
+```
+
+### Step 5: Choose Parse Mode
+
+Use AskUserQuestion:
+
+**Question:** "Which message format do you prefer?"
+
+**Options:**
+1. **Markdown (Recommended)** - Bold, italic, code blocks with Markdown syntax
+2. **HTML** - Bold, italic, code with HTML tags
+
+### Step 6: Configure Events
+
+Use AskUserQuestion with multiSelect:
+
+**Question:** "Which events should trigger Telegram notifications?"
+
+**Options (multiSelect: true):**
+1. **Session end (Recommended)** - When a Claude session finishes
+2. **Input needed** - When Claude 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 7: Write Configuration
+
+Read the existing config, merge the new Telegram settings, and write back:
+
+```bash
+CONFIG_FILE="$HOME/.claude/.omc-config.json"
+mkdir -p "$(dirname "$CONFIG_FILE")"
+
+if [ -f "$CONFIG_FILE" ]; then
+  EXISTING=$(cat "$CONFIG_FILE")
+else
+  EXISTING='{}'
+fi
+
+# BOT_TOKEN, CHAT_ID, PARSE_MODE are collected from user
+echo "$EXISTING" | jq \
+  --arg token "$BOT_TOKEN" \
+  --arg chatId "$CHAT_ID" \
+  --arg parseMode "$PARSE_MODE" \
+  '.notifications = (.notifications // {enabled: true}) |
+   .notifications.enabled = true |
+   .notifications.telegram = {
+     enabled: true,
+     botToken: $token,
+     chatId: $chatId,
+     parseMode: $parseMode
+   }' > "$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 Telegram chat
+2. **No, I'll test later** - Skip testing
+
+#### If testing:
+
+```bash
+BOT_TOKEN="USER_PROVIDED_TOKEN"
+CHAT_ID="USER_PROVIDED_CHAT_ID"
+PARSE_MODE="Markdown"
+
+RESPONSE=$(curl -s -w "\n%{http_code}" \
+  "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
+  -d "chat_id=${CHAT_ID}" \
+  -d "parse_mode=${PARSE_MODE}" \
+  -d "text=OMC test notification - Telegram is configured!")
+
+HTTP_CODE=$(echo "$RESPONSE" | tail -1)
+BODY=$(echo "$RESPONSE" | head -1)
+
+if [ "$HTTP_CODE" = "200" ]; then
+  echo "Test notification sent successfully!"
+else
+  echo "Failed (HTTP $HTTP_CODE):"
+  echo "$BODY" | jq -r '.description // "Unknown error"' 2>/dev/null || echo "$BODY"
+fi
+```
+
+Report success or failure. Common issues:
+- **401 Unauthorized**: Bot token is invalid
+- **400 Bad Request: chat not found**: Chat ID is wrong, or user hasn't sent `/start` to the bot
+- **Network error**: Check connectivity to api.telegram.org
+
+### Step 9: Confirm
+
+Display the final configuration summary:
+
+```
+Telegram Notifications Configured!
+
+  Bot:        @your_bot_username
+  Chat ID:    123456789
+  Format:     Markdown
+  Events:     session-end, ask-user-question
+
+Config saved to: ~/.claude/.omc-config.json
+
+You can also set these via environment variables:
+  OMC_TELEGRAM_BOT_TOKEN=123456789:ABCdefGHI...
+  OMC_TELEGRAM_CHAT_ID=123456789
+
+To reconfigure: /oh-my-claudecode:configure-notifications telegram
+To configure Discord: /oh-my-claudecode:configure-notifications discord
+To configure Slack: /oh-my-claudecode:configure-notifications slack
+```
+
+### Environment Variable Alternative
+
+Users can skip this wizard entirely by setting env vars in their shell profile:
+
+```bash
+export OMC_TELEGRAM_BOT_TOKEN="123456789:ABCdefGHIjklMNOpqrsTUVwxyz"
+export OMC_TELEGRAM_CHAT_ID="123456789"
+```
+
+Env vars are auto-detected by the notification system without needing `.omc-config.json`.
+
+---
+
+## Discord Setup
+
+Set up Discord notifications so OMC 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 `~/.claude/.omc-config.json`.
+
+### Step 1: Detect Existing Configuration
+
+```bash
+CONFIG_FILE="$HOME/.claude/.omc-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 Claude session finishes
+2. **Input needed** - When Claude 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. **OMC (default)** - Display as "OMC"
+2. **Claude Code** - Display as "Claude Code"
+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/.claude/.omc-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 `.omc-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}OMC 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: OMC
+
+Config saved to: ~/.claude/.omc-config.json
+
+You can also set these via environment variables:
+  OMC_DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...
+  OMC_DISCORD_MENTION=<@1465264645320474637>
+
+To reconfigure: /oh-my-claudecode:configure-notifications discord
+To configure Telegram: /oh-my-claudecode:configure-notifications telegram
+To configure Slack: /oh-my-claudecode:configure-notifications slack
+```
+
+### Environment Variable Alternative
+
+Users can skip this wizard entirely by setting env vars in their shell profile:
+
+**Webhook method:**
+```bash
+export OMC_DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
+export OMC_DISCORD_MENTION="<@1465264645320474637>"  # optional
+```
+
+**Bot API method:**
+```bash
+export OMC_DISCORD_NOTIFIER_BOT_TOKEN="your-bot-token"
+export OMC_DISCORD_NOTIFIER_CHANNEL="your-channel-id"
+export OMC_DISCORD_MENTION="<@1465264645320474637>"  # optional
+```
+
+Env vars are auto-detected by the notification system without needing `.omc-config.json`.
+
+---
+
+## Slack Setup
+
+Set up Slack notifications so OMC can message 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 `~/.claude/.omc-config.json`.
+
+### Step 1: Detect Existing Configuration
+
+```bash
+CONFIG_FILE="$HOME/.claude/.omc-config.json"
+
+if [ -f "$CONFIG_FILE" ]; then
+  HAS_SLACK=$(jq -r '.notifications.slack.enabled // false' "$CONFIG_FILE" 2>/dev/null)
+  WEBHOOK_URL=$(jq -r '.notifications.slack.webhookUrl // empty' "$CONFIG_FILE" 2>/dev/null)
+  MENTION=$(jq -r '.notifications.slack.mention // empty' "$CONFIG_FILE" 2>/dev/null)
+  CHANNEL=$(jq -r '.notifications.slack.channel // empty' "$CONFIG_FILE" 2>/dev/null)
+
+  if [ "$HAS_SLACK" = "true" ]; then
+    echo "EXISTING_CONFIG=true"
+    [ -n "$WEBHOOK_URL" ] && echo "WEBHOOK_URL=$WEBHOOK_URL"
+    [ -n "$MENTION" ] && echo "MENTION=$MENTION"
+    [ -n "$CHANNEL" ] && echo "CHANNEL=$CHANNEL"
+  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: Create a Slack Incoming Webhook
+
+Guide the user through creating a webhook if they don't have one:
+
+```
+To set up Slack notifications, you need a Slack incoming webhook URL.
+
+CREATE A WEBHOOK:
+1. Go to https://api.slack.com/apps
+2. Click "Create New App" > "From scratch"
+3. Name your app (e.g., "OMC Notifier") and select your workspace
+4. Go to "Incoming Webhooks" in the left sidebar
+5. Toggle "Activate Incoming Webhooks" to ON
+6. Click "Add New Webhook to Workspace"
+7. Select the channel where notifications should be posted
+8. Copy the webhook URL (starts with https://hooks.slack.com/services/...)
+```
+
+### Step 3: Collect Webhook URL
+
+Use AskUserQuestion:
+
+**Question:** "Paste your Slack incoming webhook URL (starts with https://hooks.slack.com/services/...)"
+
+The user will type their webhook URL in the "Other" field.
+
+**Validate** the URL:
+- Must start with `https://hooks.slack.com/services/`
+- If invalid, explain the format and ask again
+
+### Step 4: Configure Mention (User/Group Ping)
+
+Use AskUserQuestion:
+
+**Question:** "Would you like notifications to mention (ping) someone?"
+
+**Options:**
+1. **Yes, mention a user** - Tag a specific user by their Slack member ID
+2. **Yes, mention a channel** - Use @channel to notify everyone in the channel
+3. **Yes, mention @here** - Notify only active members in the channel
+4. **No mentions** - Just post the message without pinging anyone
+
+#### If user wants to mention a user:
+
+Ask: "What is the Slack member ID to mention? (Click on a user's profile > More (⋯) > Copy member ID)"
+
+The mention format is: `<@MEMBER_ID>` (e.g., `<@U1234567890>`)
+
+#### If user wants @channel:
+
+The mention format is: `<!channel>`
+
+#### If user wants @here:
+
+The mention format is: `<!here>`
+
+### Step 5: Configure Events
+
+Use AskUserQuestion with multiSelect:
+
+**Question:** "Which events should trigger Slack notifications?"
+
+**Options (multiSelect: true):**
+1. **Session end (Recommended)** - When a Claude session finishes
+2. **Input needed** - When Claude 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 Channel Override
+
+Use AskUserQuestion:
+
+**Question:** "Override the default notification channel? (The webhook already has a default channel)"
+
+**Options:**
+1. **Use webhook default (Recommended)** - Post to the channel selected during webhook setup
+2. **Override channel** - Specify a different channel (e.g., #alerts)
+
+If override, ask for the channel name (e.g., `#alerts`).
+
+### Step 7: Optional Username Override
+
+Use AskUserQuestion:
+
+**Question:** "Custom bot display name? (Shows as the webhook sender name in Slack)"
+
+**Options:**
+1. **OMC (default)** - Display as "OMC"
+2. **Claude Code** - Display as "Claude Code"
+3. **Custom** - Enter a custom name
+
+### Step 8: Write Configuration
+
+Read the existing config, merge the new Slack settings, and write back:
+
+```bash
+CONFIG_FILE="$HOME/.claude/.omc-config.json"
+mkdir -p "$(dirname "$CONFIG_FILE")"
+
+if [ -f "$CONFIG_FILE" ]; then
+  EXISTING=$(cat "$CONFIG_FILE")
+else
+  EXISTING='{}'
+fi
+
+# WEBHOOK_URL, MENTION, USERNAME, CHANNEL are collected from user
+echo "$EXISTING" | jq \
+  --arg url "$WEBHOOK_URL" \
+  --arg mention "$MENTION" \
+  --arg username "$USERNAME" \
+  --arg channel "$CHANNEL" \
+  '.notifications = (.notifications // {enabled: true}) |
+   .notifications.enabled = true |
+   .notifications.slack = {
+     enabled: true,
+     webhookUrl: $url,
+     mention: (if $mention == "" then null else $mention end),
+     username: (if $username == "" then null else $username end),
+     channel: (if $channel == "" then null else $channel 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 9: 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 Slack channel
+2. **No, I'll test later** - Skip testing
+
+#### If testing:
+
+```bash
+# For webhook:
+MENTION_PREFIX=""
+if [ -n "$MENTION" ]; then
+  MENTION_PREFIX="${MENTION}\n"
+fi
+
+curl -s -o /dev/null -w "%{http_code}" \
+  -H "Content-Type: application/json" \
+  -d "{\"text\": \"${MENTION_PREFIX}OMC test notification - Slack is configured!\"}" \
+  "$WEBHOOK_URL"
+```
+
+Report success or failure. Common issues:
+- **403 Forbidden**: Webhook URL is invalid or revoked
+- **404 Not Found**: Webhook URL is incorrect
+- **channel_not_found**: Channel override is invalid
+- **Network error**: Check connectivity to hooks.slack.com
+
+### Step 10: Confirm
+
+Display the final configuration summary:
+
+```
+Slack Notifications Configured!
+
+  Webhook:  https://hooks.slack.com/services/T00/B00/xxx...
+  Mention:  <@U1234567890> (or "none")
+  Channel:  #alerts (or "webhook default")
+  Events:   session-end, ask-user-question
+  Username: OMC
+
+Config saved to: ~/.claude/.omc-config.json
+
+You can also set these via environment variables:
+  OMC_SLACK_WEBHOOK_URL=https://hooks.slack.com/services/...
+  OMC_SLACK_MENTION=<@U1234567890>
+
+To reconfigure: /oh-my-claudecode:configure-notifications slack
+To configure Discord: /oh-my-claudecode:configure-notifications discord
+To configure Telegram: /oh-my-claudecode:configure-notifications telegram
+```
+
+### Environment Variable Alternative
+
+Users can skip this wizard entirely by setting env vars in their shell profile:
+
+```bash
+export OMC_SLACK_WEBHOOK_URL="https://hooks.slack.com/services/T00/B00/xxx"
+export OMC_SLACK_MENTION="<@U1234567890>"  # optional
+```
+
+Env vars are auto-detected by the notification system without needing `.omc-config.json`.
+
+### Slack Mention Formats
+
+| Type | Format | Example |
+|------|--------|---------|
+| User | `<@MEMBER_ID>` | `<@U1234567890>` |
+| Channel | `<!channel>` | `<!channel>` |
+| Here | `<!here>` | `<!here>` |
+| Everyone | `<!everyone>` | `<!everyone>` |
+| User Group | `<!subteam^GROUP_ID>` | `<!subteam^S1234567890>` |