investigate-errors
Investigate recent errors and exceptions in your Sentry projects
What this skill does
# Investigate Recent Errors ## Name sentry:investigate-errors - Investigate recent errors and exceptions in your Sentry projects ## Synopsis ``` /investigate-errors [arguments] ``` ## Description Investigate recent errors and exceptions in your Sentry projects to identify issues, patterns, and root causes. ## Implementation This command helps you quickly triage and investigate errors captured by Sentry across your projects. ## Usage ``` /investigate-errors [project-name] [timeframe] ``` ## What This Command Does 1. Asks for the Sentry project name (or lists available projects) 2. Requests timeframe (e.g., last 24h, last 7d, custom) 3. Fetches recent error issues using Sentry MCP tools 4. Analyzes error patterns and trends 5. Provides insights on: - Most frequent errors - Recent error spikes - Affected users/sessions - Error distribution by release/environment - Stack traces and context 6. Suggests next steps for investigation ## Prerequisites - Sentry MCP server must be installed and configured - OAuth authentication with Sentry must be completed - Access to the target Sentry project(s) ## Example Interaction ``` User: /investigate-errors my-web-app 24h Claude: Investigating errors in my-web-app for the last 24 hours... ## Error Investigation Report ### Overview - **Total Issues**: 12 error issues - **Total Events**: 347 error events - **Affected Users**: 89 unique users - **Time Range**: Last 24 hours ### Top Issues 1. **TypeError: Cannot read property 'id' of undefined** - Events: 156 - Users: 45 - First Seen: 23h ago - Last Seen: 12m ago - Environment: production - Release: v2.3.1 - Trend: Increasing (spike in last 6 hours) 2. **NetworkError: Failed to fetch user data** - Events: 89 - Users: 23 - First Seen: 18h ago - Last Seen: 1h ago - Environment: production - Release: v2.3.1 3. **ReferenceError: localStorage is not defined** - Events: 67 - Users: 34 - First Seen: 22h ago - Last Seen: 3h ago - Environment: production, staging ### Key Patterns - 45% of errors correlate with v2.3.1 deployment 23h ago - TypeError spike began 6 hours after deployment - NetworkError appears to be intermittent (API flakiness?) - localStorage errors isolated to server-side rendering context ### Recommendations 1. **Immediate**: Investigate TypeError in v2.3.1 - likely regression in user data handling 2. **High Priority**: Check API stability for fetch failures 3. **Medium Priority**: Add server-side rendering guards for localStorage access Would you like me to dive deeper into any specific error? ``` ## Arguments - `project-name` (optional): Sentry project slug - `timeframe` (optional): Time range (1h, 24h, 7d, 30d, or custom) ## Tips - Start with shorter timeframes for faster investigation - Look for error spikes that correlate with deployments - Use error grouping to identify patterns - Check release and environment tags for correlation - Review stack traces for common code paths - Use Seer AI for automated root cause analysis ## Related Commands - `/analyze-performance`: Investigate performance issues - `/check-releases`: Review recent release health - `/query-events`: Run custom Sentry queries
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.