tech-errors-watcher

Automating Datadog alert triage from Slack involves monitoring channels like #tech_errors, cross-referencing metrics with logs and GitHub deploy history, and identifying root causes. This skill handles the end-to-end workflow, escalating unhandled alerts to deep analysis to pinpoint issues automatically.

Yes, you can automatically create GitHub PRs from production monitoring alerts. When high-confidence evidence identifies a specific code change as the root cause, the automation creates a scoped fix PR from a dedicated worktree, enables auto-merge, and monitors CI status until merged.

Evidence-based fix gating for incident response requires very high confidence that a specific change caused the alert before proposing fixes. It aggregates Datadog context, log samples, and GitHub deploy history as evidence, routing all approval requests through a standardized Slack YES/NO workflow.

Setting up Slack automation for tech error alerts requires integration with Slack, Datadog, logs.sh, and GitHub. You also need the $handle-in-slack approval workflow to gate all side-effect actions, ensuring that operational changes and PR creations receive explicit human approval before execution.

Preventing duplicate incident response work on active Datadog alerts is achieved by checking existing triage and PR threads before taking action. The automation watches Slack channels, escalates unhandled alerts, and avoids redundant effort by cross-referencing ongoing mitigation activities.

If the automated alert watcher stops running or gets deleted, a daily repair cron automatically recovers the core watcher automation. This self-healing mechanism ensures the Slack monitoring, triage, and PR gating workflows remain active without requiring manual intervention or restarts.