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}`.
**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
ALERT_OUT=$(bash "$REPO_ROOT/.claude/scripts/post-bot-alert.sh" "<message>")