error-pulse

Investigate PostHog alerts, classify incidents, and escalate via Slack workflows.

198|19|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/iterate/iterate --skill error-pulse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-pulse
Source: https://github.com/iterate/iterate/tree/main/.opencode/skills/error-pulse
Command: npx skills add https://github.com/iterate/iterate --skill error-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Error Pulse helps you respond to PostHog alerts quickly by organizing investigation, classification, and escalation so incidents get resolved with minimal human toil.

Core Features & Use Cases

  • Evidence-first investigation: Collect concrete proof (logs, traces, failing checks, repro steps) and verify whether the regression exists in the iterate repo.
  • Triage and classification: Decide between false positive/noisy alert tuning and real-bug fixes with minimal safe changes, plus testing and logging improvements when needed.
  • Actionable Slack escalation: Post to #error-pulse using required deep-links inline and follow autonomous merge safety gates when attempting merges.

Use case: You receive a PostHog alert for an exception; you gather the exact error event link and a Worker logs deep-link, pinpoint whether it’s a regression in apps/os, and either implement a smallest safe fix or open a targeted discussion for noise reduction.

Quick Start

Use the error-pulse skill to investigate a PostHog alert, classify it as noise or a real bug, and escalate in #error-pulse with the required PostHog, Cloudflare logs, and source-code deep-links included in the first message.

Frequently Asked Questions about error-pulse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage PostHog alerts for Cloudflare Workers regressions?

Triage PostHog alerts by collecting concrete evidence like Worker logs and source permalinks, verifying the regression in your repo, and classifying it as a real bug or noisy alert before escalating to Slack.

What is the best way to escalate incident alerts to Slack with required deep-links?

Escalate incident alerts to Slack by posting to the designated channel with first-message deep-links to the PostHog error event, Cloudflare Worker logs, and a GitHub source permalink included inline.

How do I classify whether a PostHog exception alert is noise or a real bug?

Classify a PostHog exception alert by gathering exact error event links and Worker logs, pinpointing if the regression exists in your codebase, and deciding between noise tuning or implementing a minimal safe fix.

Can I autonomously merge fixes when responding to incident alerts?

You can autonomously merge fixes only when strict merge safety gates are satisfied, ensuring that changes are minimal, safe, and properly tested before coordinating the merge for the incident response.

What deep-links do I need to investigate PostHog exceptions in Cloudflare Workers?

Investigating PostHog exceptions requires a PostHog error event link, a Cloudflare Worker logs deep-link with a prefilled regex when possible, and a GitHub source permalink to verify the regression.