azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(alerts): route RMM/Dev alerts to private #dev-alerts, Syncro stays in #bot-alerts

Browse Source 
post-bot-alert.sh now auto-routes by message prefix: [RMM]/[DEPLOY]/[DEV]/[BUILD]/
[GURURMM]/[SMARTBADGE-WATCH] -> #dev-alerts (1509998508198068484, private; Howard+Mike);
everything else incl. [SYNCRO] -> #bot-alerts (unchanged). Optional 2nd arg (dev|bot|
<channel_id>) overrides. Existing call sites (scheduled SmartBadge task, /rmm) route
correctly with no change. /rmm skill docs updated to reference #dev-alerts.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-05-29 12:18:49 -07:00
parent 70d21901a6
commit 95daa70551
2 changed files with 32 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.claude/commands/rmm.md
View File

@@ -60,7 +60,7 @@ Interact with the GuruRMM agent fleet: list agents, run remote commands (PowerSh
**Heredoc payloads — always use `--data-binary @-` and `<<'JSON'` for static payloads.** On Windows, the Write tool and Git Bash resolve `/tmp/foo.json` to different directories. Heredoc avoids the file handoff entirely. Use `<<'JSON'` (single-quoted) for static payloads that contain no shell variables; use `<<JSON` (unquoted) when interpolating `${VARS}`. **Heredoc payloads — always use `--data-binary @-` and `<<'JSON'` for static payloads.** On Windows, the Write tool and Git Bash resolve `/tmp/foo.json` to different directories. Heredoc avoids the file handoff entirely. Use `<<'JSON'` (single-quoted) for static payloads that contain no shell variables; use `<<JSON` (unquoted) when interpolating `${VARS}`.
**After every dispatch: post a one-line alert to #bot-alerts.** Same rule as Syncro — write operations (dispatch + cancel) get a bot alert. Read operations (list, status, output) do not. **After every dispatch: post a one-line alert.** RMM alerts go to the private **#dev-alerts** (Howard + Mike) — `post-bot-alert.sh` auto-routes any `[RMM]`/`[DEPLOY]`-prefixed message there. Write operations (dispatch + cancel) get an alert; read operations (list, status, output) do not.
--- ---
@@ -591,9 +591,9 @@ For complex multi-step remediation (move files, install software, configure serv
--- ---
## Post to #bot-alerts (after every write) ## Post to #dev-alerts (after every write)
Post after every successful dispatch or cancel. Never post for read-only operations. Post after every successful dispatch or cancel. Never post for read-only operations. RMM alerts route to the private **#dev-alerts** channel automatically (the `[RMM]` prefix triggers auto-routing in `post-bot-alert.sh`); no channel argument needed.
```bash ```bash
ALERT_OUT=$(bash "$REPO_ROOT/.claude/scripts/post-bot-alert.sh" "<message>") ALERT_OUT=$(bash "$REPO_ROOT/.claude/scripts/post-bot-alert.sh" "<message>")

33
.claude/scripts/post-bot-alert.sh
View File

@@ -1,8 +1,15 @@
#!/usr/bin/env bash #!/usr/bin/env bash
# post-bot-alert.sh — post a one-line message to the Discord #bot-alerts channel. # post-bot-alert.sh — post a one-line message to a Discord alert channel.
#
# Routing: #bot-alerts (default; Syncro + general, whole team) vs #dev-alerts
# (private; RMM/Dev alerts, Howard + Mike only). Auto-routes by message prefix:
# [RMM] [DEPLOY] [DEV] [BUILD] [GURURMM] [SMARTBADGE-WATCH] -> #dev-alerts;
# everything else (incl. [SYNCRO]) -> #bot-alerts. Override with a 2nd arg.
# #
# Usage: # Usage:
# bash post-bot-alert.sh "message text" # bash post-bot-alert.sh "message text" # auto-route by prefix
# bash post-bot-alert.sh "message text" dev # force #dev-alerts
# bash post-bot-alert.sh "message text" bot # force #bot-alerts
# echo "message text" | bash post-bot-alert.sh # echo "message text" | bash post-bot-alert.sh
# #
# Token resolution (first hit wins): # Token resolution (first hit wins):
@@ -16,7 +23,8 @@
set -u set -u
CHANNEL_ID="624710699771232265" # #bot-alerts (Arizona Computer Guru guild) BOT_CHANNEL_ID="624710699771232265" # #bot-alerts — default (Syncro + general; whole team)
DEV_CHANNEL_ID="1509998508198068484" # #dev-alerts — private RMM/Dev alerts (Howard + Mike only)
ROOT="${CLAUDETOOLS_ROOT:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)}" ROOT="${CLAUDETOOLS_ROOT:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)}"
# --- message (arg or stdin) --- # --- message (arg or stdin) ---
@@ -27,6 +35,23 @@ if [ -z "$MSG" ]; then
exit 0 exit 0
fi fi
# --- channel routing ---
# Optional 2nd arg: "dev"/"bot" keyword, a raw channel id, or omit for auto.
# Auto: RMM/Dev-category prefixes -> #dev-alerts (private); everything else
# (Syncro, general) -> #bot-alerts. Keeps existing call sites correct unchanged.
TARGET="${2:-auto}"
case "$TARGET" in
dev|dev-alerts) CHANNEL_ID="$DEV_CHANNEL_ID"; CHANNEL_NAME="#dev-alerts" ;;
bot|bot-alerts) CHANNEL_ID="$BOT_CHANNEL_ID"; CHANNEL_NAME="#bot-alerts" ;;
auto|"")
if printf '%s' "$MSG" | grep -qiE '^\[(RMM|DEPLOY|DEV|BUILD|GURURMM|SMARTBADGE-WATCH)\b'; then
CHANNEL_ID="$DEV_CHANNEL_ID"; CHANNEL_NAME="#dev-alerts"
else
CHANNEL_ID="$BOT_CHANNEL_ID"; CHANNEL_NAME="#bot-alerts"
fi ;;
*) CHANNEL_ID="$TARGET"; CHANNEL_NAME="channel ${TARGET}" ;;
esac
# --- token: vault first, then .env --- # --- token: vault first, then .env ---
TOKEN="$(bash "$ROOT/.claude/scripts/vault.sh" get-field \ TOKEN="$(bash "$ROOT/.claude/scripts/vault.sh" get-field \
projects/discord-bot/bot-token.sops.yaml credentials.bot_token 2>/dev/null)" projects/discord-bot/bot-token.sops.yaml credentials.bot_token 2>/dev/null)"
@@ -56,7 +81,7 @@ BODY="$(printf '%s' "$RESP" | sed '$d')"
if [ "$HTTP" = "200" ]; then if [ "$HTTP" = "200" ]; then
MID="$(printf '%s' "$BODY" | jq -r '.id // empty' 2>/dev/null)" MID="$(printf '%s' "$BODY" | jq -r '.id // empty' 2>/dev/null)"
echo "[OK] post-bot-alert: posted to #bot-alerts (message_id=${MID})" echo "[OK] post-bot-alert: posted to ${CHANNEL_NAME} (message_id=${MID})"
exit 0 exit 0
fi fi