Menu
Send Slack messages, alerts, and notifications. Use for routing finding alerts to owner teams, broadcasting CI failures, or announcing PR-ready status.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Launch and drive the Gatherly app locally (FastAPI backend + Next.js frontend) and verify it renders. Use when asked to run, start, launch, or screenshot the app, or to confirm a change works in the real running app.
Scan code for security violations S1-S8 (auth, tenant isolation, RBAC, rate limiting, audit logging, raw SQL, secrets, HTTP timeouts). Use before commit on any code touching endpoints, services, or data access.
Run the event-readiness checklist against an event. Evaluates the readiness checks, produces findings, and routes them to the host. Use when the user asks to audit, score, or check the readiness of an event.
Commit changes with the dev-gatherly git identity using Conventional Commits format. Use after every atomic step in the REPL loop.
Push the current branch and create a production-ready PR with a complete description (What, Why, How to test). Runs /review-pr first if not already done. Use when implementation is complete.
Monitor CI/CD pipeline runs, diagnose failures, and route fixes to the right phase. Use after pushing a branch or when a pipeline turns red.
| name | notify |
| description | Send Slack messages, alerts, and notifications. Use for routing finding alerts to owner teams, broadcasting CI failures, or announcing PR-ready status. |
| allowed-tools | Bash, Read |
Local setup: requires the Slack MCP (
SLACK_BOT_TOKEN,SLACK_TEAM_ID), not configured in this repo. Without it, surface the message text in the conversation instead of posting.
You send Slack messages on behalf of Gatherly. Messages are concise, actionable, and routed to the right channel.
/notify <channel> <message>
/notify finding GA-F-1234 # Send a readiness-check alert to the event host
/notify pr <pr-number> # Announce a PR-ready status
/notify ci-fail <run-id> # Broadcast a CI failure
/notify deploy <env> # Announce a deployment
🟠 New HIGH severity readiness check failed on `summer-launch-party`
Checklist: Event Readiness
Check: within_capacity
Evidence: 142 RSVP=yes exceeds capacity of 120
Auto-fixable: ✅ — queued for /work-findings
Track: <link to finding>
🚨 CI failed on `feat/waitlist-auto-promote`
Job: test (run #4523)
Failed: tests/services/test_guest_service.py::test_promote_waitlisted_concurrent
Cause: race condition in waitlist promotion
Diagnostics: <link to /devops report>
Triggered by: @<user>
👀 PR ready for review
#87 — feat(be): add event readiness checklist with comparison
Branch: feat/F-12-readiness-checklist
Tests: ✅ 147 pass | Audit: ✅ clean | Review: ✅ no critical bugs
→ <PR link>
🚀 Deployed to `staging`
Commit: a1b2c3d feat(be): add event readiness checklist
By: @dev-gatherly (auto)
Pipeline: <link>
Rollback: gh workflow run rollback.yml -F env=staging
🔴 P0 — production incident
Issue: cross-owner data leakage in guests API
Detected by: /audit-security (finding GA-A-2026-05-12-44)
Triage: <issue link>
Page on-call: <pagerduty link>
| Source | Default channel |
|---|---|
Readiness check for event <event> | #<host-slack> (from host config) |
| CI failure on main | #gatherly-alerts |
| PR ready | #gatherly-prs |
| Deployment | #gatherly-deploys |
| P0/P1 incident | #gatherly-alerts AND #incidents |
| General announcement | #gatherly-team |
If the event host has no Slack channel configured: fall back to #gatherly-orphans and add a note that the finding needs host routing setup.
@here or @channel for routine notifications