claudetools/.claude/memory/feedback_no_botalerts_internal_rmm.md at 044ff84b0793aebaf9678fc83fc3aca7fa67e41c

Files

Mike Swanson 0daa7951b3 sync: auto-sync from GURU-5070 at 2026-06-02 07:25:49

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-02 07:25:49

2026-06-02 07:25:55 -07:00

1.2 KiB

Raw Blame History

name, description, metadata

name

description

metadata

feedback_no_botalerts_internal_rmm

Post

type
feedback

The /rmm skill instructs "post a one-line #bot-alert after every dispatch." Mike does NOT want #bot-alerts for internal infrastructure / dev-tooling commands — e.g. installing a Gitea Actions runner on PLUTO, CI/build orchestration on build VMs, inventory/recon during setup.

The rule (Mike, 2026-05-29): post a #bot-alert ONLY when the RMM command directly affects a client endpoint or a ticket (remediation, a client machine change, ticket-linked work). For everything else — internal infra, build/CI orchestration, dev-tooling, recon/inventory (e.g. the PLUTO build-runner setup) — SKIP the alert.

Why: keeps #bot-alerts signal-high — it's a client/ticket activity feed, not a build log.

How to apply: When dispatching via /rmm or the GuruRMM command API, ask "does this touch a client/ticket?" If no, do NOT call post-bot-alert.sh. Overrides the skill's blanket "alert after every dispatch" rule. Related: reference_pluto_build_server.

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History