# Diagnose Errors and Resolve Incidents

Complex application failures are difficult to isolate across logs, traces, deployments, and services. This skill structures evidence, root-cause analysis, fixes, tests, and prevention.

## Install

```bash
npx skillstore add sickn33/error-diagnostics-error-analysis
```

## Metadata

- Status: approved
- Slug: sickn33-error-diagnostics-error-analysis
- Skillstore revision: r2
- Version status: missing
- Tree hash: 28837784e505f98161447557b3f5db6f7c3d1d61d628be7e7dc276aa4d7575af
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-diagnostics-error-analysis
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, network, env\_access
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-error-diagnostics-error-analysis
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-error-diagnostics-error-analysis/manifest

## Capabilities

- Classifies errors by severity, type, observability, and user impact.
- Guides root-cause analysis using reproduction, isolation, call chains, state inspection, and hypothesis testing.
- Correlates logs, traces, metrics, deployments, and service dependencies across distributed systems.
- Proposes immediate fixes, validation tests, rollback plans, and preventive measures.
- Provides patterns for structured logging, correlation IDs, retries, circuit breakers, monitoring, and alerts.
- Structures incident summaries, timelines, evidence, runbooks, and stakeholder updates.

## Use Cases

- Investigate a Production Incident: Correlate symptoms, timelines, logs, traces, and deployments to identify a supported root-cause hypothesis.
- Debug a Recurring Application Error: Narrow a failure, inspect its call path, and define focused tests for the proposed fix.
- Improve Service Observability: Review error handling and recommend structured logs, correlation identifiers, tracing, monitoring, and alert thresholds.

## Prompt Templates

### Explain an Error

```
Analyze this error message and stack trace: [details]. Explain the likely failure point, missing context, and three next checks.
```

### Diagnose a Recurring Failure

```
Investigate this recurring error using the supplied logs and reproduction steps: [details]. Rank hypotheses by evidence and propose targeted tests.
```

### Analyze a Distributed Incident

```
Build an incident timeline from these logs, traces, metrics, and deployments: [details]. Identify affected services, root cause, mitigation, and validation steps.
```

### Design a Prevention Plan

```
Review this completed incident analysis: [details]. Design code fixes, regression tests, observability improvements, alerts, rollback controls, and a reusable runbook.
```

## Limitations

- Requires relevant error messages, logs, traces, metrics, or reproduction details.
- Cannot confirm a root cause without environment-specific evidence and validation.
- Does not replace production access controls, change approval, or expert review.
- Examples require adaptation to the user's frameworks, services, and observability tools.

## Best Practices

- Redact secrets and personal data before sharing diagnostics.
- Separate observed evidence from hypotheses and state confidence clearly.
- Validate fixes with focused tests, production-like conditions, monitoring, and rollback criteria.

## Anti Patterns

- Do not change production systems without approval, safeguards, and a rollback plan.
- Do not conclude root cause from one symptom or an isolated log line.
- Do not add broad retries without limits, backoff, jitter, and error classification.

## Security Audit

- Audited at: 2026-07-23T23:48:17.337\+00:00
- Summary: All 39 static alerts are false positives caused by inert Markdown examples, template literals, placeholder endpoints, or ordinary technical prose. The skill contains no executable scripts or automatic network, environment, or command access. No prompt injection or malicious intent was found.

## Stats

- Views: 112
- Downloads: 11
- Favorites: 0
- Popularity score: 0