investigating-error-issue
Installation
SKILL.md
Investigating an error tracking issue
When a user asks "what's going on with this error?" or pastes an issue URL, gather the context they would otherwise have to assemble manually: who is hitting it, what changed, where it happens, and whether a replay shows the cause.
Available tools
| Tool | Purpose |
|---|---|
posthog:query-error-tracking-issue |
Compact issue details (status, assignee, top frame, release, aggregates) |
posthog:query-error-tracking-issue-events |
Sampled $exception events with stack, URL, browser, $session_id |
posthog:execute-sql |
Breakdowns, release / flag correlations, surrounding events + console logs around the error |
posthog:query-logs |
OTEL log entries around the error timestamp for server-side issues |
posthog:query-session-recordings-list |
Linked replays (delegate ranking to finding-replay-for-issue) |
posthog:read-data-schema |
Confirm property keys before filtering on them |