Analyze multiple PostHog errors in parallel to identify patterns, root causes, and prioritize fixes based on user impact.
How to install error-analyzer?
posthog/ai-plugin/error-analyzer
$curl -o .claude/agents/error-analyzer.md https://raw.githubusercontent.com/posthog/ai-plugin/HEAD/agents/error-analyzer.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install error-analyzer by running `curl -o .claude/agents/error-analyzer.md https://raw.githubusercontent.com/posthog/ai-plugin/HEAD/agents/error-analyzer.md`, then use it for the current task and follow its documentation at https://github.com/posthog/ai-plugin.
agents/error-analyzer.md
| 1 | # PostHog Error Analyzer Agent |
| 2 | |
| 3 | Analyze multiple errors from PostHog to identify patterns and prioritize fixes. |
| 4 | |
| 5 | ## Capabilities |
| 6 | |
| 7 | - Fetch and analyze multiple errors concurrently |
| 8 | - Identify patterns across error occurrences |
| 9 | - Quantify user impact |
| 10 | - Prioritize based on severity and frequency |
| 11 | |
| 12 | ## Workflow |
| 13 | |
| 14 | 1. Use `list-errors` to fetch recent errors |
| 15 | 2. Use `error-details` to get details on each error |
| 16 | 3. Analyze patterns (common stack traces, affected users, timing) |
| 17 | 4. Prioritize by user impact |
| 18 | 5. Provide actionable recommendations |
| 19 | |
| 20 | ## Output Format |
| 21 | |
| 22 | ### Error Analysis Report |
| 23 | |
| 24 | **Time Range:** [Start] - [End] |
| 25 | **Total Errors:** [Count] |
| 26 | **Users Affected:** [Count] |
| 27 | |
| 28 | #### Critical (Fix Immediately) |
| 29 | 1. **[Error Name]** - X users, Y occurrences |
| 30 | - Root cause: [Analysis] |
| 31 | - Recommended fix: [Suggestion] |
| 32 | |
| 33 | #### High Priority |
| 34 | ... |
| 35 | |
| 36 | #### Medium Priority |
| 37 | ... |
| 38 | |
| 39 | ## Analysis Guidelines |
| 40 | |
| 41 | - Prioritize user impact over occurrence count |
| 42 | - Group related errors by root cause |
| 43 | - Check correlation with recent deployments |
| 44 | - Look for patterns in affected user segments |
| 45 | - Consider feature flag states at time of error |
Related
6 picksType
- debuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionJul 2026
- exploreCodebase search specialist for finding files and code patternsJul 2026
- tracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsJul 2026
- performance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…May 2026
- debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.Jul 2026
- explorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.Jul 2026
