# Diagnose Errors and Resolve Production Incidents

Complex failures can hide across logs, traces, services, and recent changes. This skill structures evidence, tests hypotheses, and recommends fixes with prevention steps.

## Install

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

## Metadata

- Status: approved
- Slug: sickn33-error-debugging-error-analysis
- Skillstore revision: r2
- Version status: missing
- Tree hash: 74f49c985c2b20a6d1859f52702acbbeab137339e418a329b016c9517bd4462d
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-debugging-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-debugging-error-analysis
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-error-debugging-error-analysis/manifest

## Capabilities

- Classifies errors by severity, type, observability, and likely user impact.
- Analyzes stack traces, logs, timestamps, correlation identifiers, and service dependencies.
- Builds incident timelines and ranks root-cause hypotheses using available evidence.
- Proposes targeted reproduction steps and experiments to validate suspected causes.
- Recommends fixes, regression tests, rollback plans, and preventive controls.
- Suggests structured logging, tracing, monitoring, and alerting improvements.

## Use Cases

- Debug an Application Failure: Analyze an exception and stack trace, isolate the failing path, and define focused verification steps.
- Investigate a Production Incident: Correlate logs, traces, deployments, and service dependencies to build a timeline and identify likely root causes.
- Prevent Recurring Errors: Turn incident evidence into corrective actions for tests, monitoring, alerting, ownership, and rollback readiness.

## Prompt Templates

### Explain an Error

```
Analyze this error message and stack trace: [details]. Identify the likely cause, explain the evidence, and suggest safe verification steps.
```

### Investigate a Recurring Failure

```
Investigate this recurring failure using these logs and timestamps: [details]. Group patterns, rank hypotheses, and propose targeted experiments.
```

### Trace a Distributed Incident

```
Analyze this cross-service incident using logs, traces, deployment history, and service dependencies: [details]. Build a timeline and identify the root cause.
```

### Design a Prevention Plan

```
Review this resolved incident: [details]. Create corrective actions covering code fixes, tests, observability, alerting, rollback readiness, and ownership.
```

## Limitations

- Requires relevant error messages, logs, traces, or reproducible symptoms.
- Cannot verify hypotheses without access to the affected code and environment.
- Does not replace production testing, operational approval, or expert review.
- Observability examples require adaptation for each stack, vendor, and privacy policy.

## Best Practices

- Provide exact timestamps, versions, error messages, and affected services.
- Separate observed evidence from assumptions and test each hypothesis.
- Redact secrets and personal data before sharing logs or traces.

## Anti Patterns

- Do not change production systems without approval and a rollback plan.
- Do not treat the final stack frame as the root cause without tracing inputs.
- Do not add broad retries without checking idempotency and retryable failures.

## Security Audit

- Audited at: 2026-07-23T23:35:36.361\+00:00
- Summary: All 39 static findings are false positives caused by fenced examples, template literals, reserved addresses, prose, or Markdown. The files contain debugging guidance and safety cautions; no executable payload, prompt injection, credential collection, or covert network behavior was found.

## Stats

- Views: 127
- Downloads: 13
- Favorites: 0
- Popularity score: 0