1k-sentry-analysis

Analyze Sentry crash reports and generate bug analysis logs for the OneKey monorepo.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill 1k-sentry-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1k-sentry-analysis
Source: https://github.com/wanghaisheng/web3-scaffold-app-monorepo/tree/main/.claude/skills/1k-sentry-analysis
Command: npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill 1k-sentry-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This guide provides a complete workflow for analyzing and fixing production errors reported by Sentry crashes within the OneKey app monorepo. It ensures structured bug analysis, traceable root-cause deduction, and repeatable resolutions that can be reviewed and reused across projects.

Core Features & Use Cases

  • Bug analysis logs are generated in node_modules/.cache/bugs/ before any code changes.
  • Evidence-based root-cause analysis using six types of proof (stack traces, breadcrumbs, timing, etc.) to build a complete causation chain.
  • End-to-end remediation workflow from detection to PR creation, including testing plans and prevention recommendations.
  • Reusable templates and references to guide developers in diagnosing Sentry events and communicating fixes.

Quick Start

Follow the steps to create a bug analysis document and begin the fix workflow.

Frequently Asked Questions about 1k-sentry-analysis

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

FAQPage Schema
How do I analyze Sentry crash reports for production issues?

To analyze Sentry crash reports for production issues, you apply an evidence-based workflow that uses stack traces and breadcrumbs to deduce root causes before generating bug analysis logs and fix proposals.

What is the best way to triage AppHang and ANR events in a monorepo?

Triageing AppHang and ANR events in a monorepo requires systematically collecting Sentry JSON logs and creating traceable bug analysis documents to build a complete causation chain before implementing fixes.

How do I create a bug analysis log before fixing Sentry crashes?

You create a bug analysis log before fixing Sentry crashes by generating a document under node_modules/.cache/bugs/ in your local development environment to record evidence and root-cause deduction.

Does Sentry error analysis require a local development environment setup?

Sentry error analysis requires a local development environment setup to access Sentry JSON logs, generate cache files for bug analysis, and allow a reviewer to confirm before implementing production fixes.

What types of proof are used for Sentry root-cause analysis?

Sentry root-cause analysis uses six types of proof, including stack traces, breadcrumbs, and timing data, to construct a complete causation chain for diagnosing production crash events.

When should I not use a structured Sentry bug triage workflow?

You should not bypass a structured Sentry bug triage workflow when dealing with production crashes, as skipping bug analysis logs and reviewer confirmation risks untraceable resolutions and repeatable errors.