Results for “crash-analysis”

Analyze core dumps, debug live processes, and investigate crashes, deadlocks, or memory issues in C/C++ programs using GDB with intelligent source code correlation.

Incident Report (Blameless RCA)

在启动一个重要项目或关键行动之前，用于主动识别和防范风险

`analysis-agent`/`task-agent`/`review-agent`: use when symptoms, logs, metrics, regressions, or incidents need cause analysis; skip when no diagnosis decision exists.

Analyzes .NET project code coverage and CRAP (Change Risk Anti-Patterns) scores to identify risk hotspots, methods blocking coverage gains, and prioritize where to add tests.

Guide a team through writing a structured, blameless post-mortem after a production incident, covering timeline reconstruction, root cause analysis, impact quantification, and action item generation.

Analyzes the downstream impact (blast radius) when a BigQuery table or view is broken, stale, or modified, identifying all affected downstream tables, dashboards, and processes.

Fetches and summarizes TestFlight crash reports, beta feedback, and performance diagnostics using the asc CLI.

Maps external dependencies and I/O boundaries, generates chaos tests for failure modes like timeouts and connection errors, runs them, and reports resilience gaps with fixes.

Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.

Use this skill when the user asks about accident claims management — first-notice-of-loss procedures, working with insurance adjusters, claim severity classification, subrogation, claim closure timelines, and how to influence claim outcomes. Different from accident-investigation-playbook (which covers facts); this covers the insurance + claim side.

Conduz investigação de incidentes com método: triagem, hipóteses, mitigação, RCA e postmortem, priorizando evidências e confirmação humana.

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

Analyze core dumps, debug live processes, and investigate crashes, deadlocks, and memory issues in C/C++ programs using GDB with source code correlation.

`analysis-agent`/`task-agent`/`review-agent`: use for recurrence guards on known defects, incidents, or escaped failures; skip speculative risk without a prior failure mechanism.

Challenge

Use this skill when a crash has been incorrectly classified as DOT-recordable when it shouldn't be. Covers the § 390.5 criteria, common misclassifications, and challenge process.

Breaks down current state, context, user input, and data into a structured assessment before taking action.

`analysis-agent`/`task-agent`/`review-agent`: use when repeated failure needs a new hypothesis or proof path; skip an initial failure with verified cause and a different action.

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

`analysis-agent`/`task-agent`/`review-agent`: primary-Skill-selected for races, locks, optimistic conflicts, or worker overlap; never task owner; skip without concurrency impact.

当分析个人或他人成就差异的根本原因，并寻求提升路径时

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

`analysis-agent`: use when a request needs normal, failure, edge, abuse, recovery, or operational scenarios; skip when no scenario-decomposition decision exists.

Guides a blameless post-mortem process for incidents, covering templates, root-cause analysis, action items, and prevention.

Responding to incidents: identifies impact scope, formulates recovery procedures, creates postmortems. Use when incident response or disaster recovery is needed. Delegates fixes to Builder.

Analyze conversion funnel drop-offs and identify biggest leak points with impact-ranked recommendations

Implements error tracking and crash reporting in Flutter apps using Sentry and Firebase Crashlytics, including automatic error capture, enriched context, breadcrumbs, and CI/CD integration for source maps and debug symbols.

Runs full Trailmark structural analysis by building a graph and computing pre-analysis passes for hotspots, taint, blast radius, privilege boundaries, and attack surface.

Design, run, and learn from safe chaos engineering experiments with structured plans, blast radius calculation, and postmortem generation.

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates.

Analyzing pre-change impact across vertical (dependency chains, files) and horizontal (pattern consistency, naming) dimensions. Use to estimate blast radius before a refactor. No code.

Routes runtime-log requests into an evidence packet to isolate the first actionable blocker, repeated signature, blast radius, or safest next read-only check.