Loading...
Loading...
Found 72 Skills
Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (`/error_tracking/<id>`) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.
Upload sourcemaps and symbol files to PostHog error tracking with posthog-cli. Use in release/build steps that must make stack traces readable. Not for analytics queries or app instrumentation.
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
Sentry error tracking and debugging specialist
PostHog integration for any Ruby application using the Ruby SDK
Use when capturing and reporting errors to Sentry, adding context, or handling exceptions. Covers error boundaries, context enrichment, and fingerprinting.
PostHog integration for Next.js Pages Router applications
PostHog integration for React applications built with Vite (no router)
Store failed jobs for replay or manual inspection. Track failure patterns, enable manual intervention, and prevent data loss from processing errors.
Execute advanced Sentry troubleshooting techniques. Use when debugging complex SDK issues, missing events, source map problems, or performance anomalies. Trigger with phrases like "sentry not working", "debug sentry", "sentry events missing", "fix sentry issues".
PostHog integration for Laravel applications
Capture exceptions, add context, create performance spans, and use structured logging with Sentry.