# Diagnose Errors with Structured Debugging

Complex failures create scattered evidence and uncertain fixes. This skill organizes errors, telemetry, hypotheses, fixes, validation, and prevention into one debugging workflow.

## Install

```bash
npx skillstore add sickn33/error-diagnostics-smart-debug
```

## Metadata

- Status: approved
- Slug: sickn33-error-diagnostics-smart-debug
- Skillstore revision: r2
- Version status: missing
- Tree hash: f5f672986a8a7a72cebdcc9deed66a9c010a7720d1e0292d76303f4e958f494e
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-diagnostics-smart-debug
- 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: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-error-diagnostics-smart-debug
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-error-diagnostics-smart-debug/manifest

## Capabilities

- Parses reported errors, stack traces, reproduction steps, affected components, environments, and failure patterns.
- Produces three to five ranked root cause hypotheses with evidence, probability, falsification criteria, and tests.
- Recommends debugging strategies based on reproducibility, environment, traffic behavior, and available observability data.
- Identifies useful breakpoint, logpoint, trace, and instrumentation locations across code paths and integration boundaries.
- Structures fix proposals with impact, risk, test coverage, rollback, validation, and prevention steps.
- Defines post-fix success criteria covering tests, performance, error rates, and edge cases.

## Use Cases

- Debug Application Failures: Turn a reproducible error and stack trace into ranked causes, targeted tests, and a validation plan.
- Investigate Production Incidents: Correlate logs, traces, metrics, and deployments to isolate intermittent service failures.
- Review High-Risk Fixes: Assess proposed fixes, rollout risks, test coverage, rollback steps, and prevention measures before release.

## Prompt Templates

### Triage an Error

```
Summarize this error and list the missing information needed for triage: [error and context].
```

### Rank Root Causes

```
Analyze this stack trace. Provide three ranked hypotheses, supporting evidence, falsification criteria, and the next test for each: [stack trace].
```

### Compare Observability Data

```
Compare these successful and failed request traces. Identify divergence points and recommend targeted instrumentation: [observability data].
```

### Plan a Production Fix

```
Build a production-safe analysis and fix plan for this intermittent incident. Include rollout, rollback, validation, and prevention: [incident evidence].
```

## Limitations

- Requires the user to provide accurate error details, code context, logs, traces, or metrics.
- Does not independently access Sentry, DataDog, production systems, source repositories, or deployment platforms.
- Cannot confirm a root cause without environment-specific testing and evidence.
- Recommendations may require permissions and safeguards before production instrumentation or traffic changes.

## Best Practices

- Provide complete error messages, timestamps, environments, reproduction steps, and recent deployment details.
- Separate observations from assumptions, and require evidence plus falsification criteria for every hypothesis.
- Use protected, sampled, and reversible instrumentation before making production changes.

## Anti Patterns

- Do not choose a root cause from an error message without checking logs, traces, code, and timing.
- Do not enable broad production logging that may expose sensitive data or create excessive load.
- Do not deploy a fix without regression tests, monitoring, rollback steps, and measurable success criteria.

## Security Audit

- Audited at: 2026-07-23T23:54:31.59\+00:00
- Summary: All three static findings are false positives caused by Markdown syntax or ordinary checklist text in SKILL.md. The skill contains no shell execution, network reconnaissance, or intent-level security issue.

## Stats

- Views: 106
- Downloads: 10
- Favorites: 0
- Popularity score: 0