Skip to main content
skill CX Codex

error-diagnostics-smart-debug — Claude Code skill

The error-diagnostics-smart-debug skill investigates failures through reproduction steps, traces, logs, and code, then guides hypothesis testing and scoped fix validation.

MIT 1 installs ★ 50,109 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill error-diagnostics-smart-debug -a claude-code
Open on GitHub

What error-diagnostics-smart-debug does

The skill starts by extracting the error pattern, reproduction details, affected components, runtime environment, and failure frequency. It ranks several possible causes, ties each one to evidence, and sets out a test that could confirm or disprove it. The workflow can choose local interactive debugging, observability analysis, time-travel debugging, controlled fault reproduction, or delta debugging.

For staging and production incidents, it can organize checks across Sentry, Rollbar, Bugsnag, DataDog, New Relic, Dynatrace, Jaeger, Zipkin, Honeycomb, and log aggregation systems. It then describes the proposed code change, impact, risk, test coverage, rollback, and post-fix verification. A debugger subagent is used only with user approval and when the host exposes that capability.

The skill also covers regression tests, alerts, runbook updates, and monitoring for similar failures. Production instrumentation, debug endpoints, and traffic shifts require review of authorization, redaction, duration, rollback, and target before use.

What it helps with

  • trace a failure from logs and distributed traces
  • compare an error with source and deployment changes
  • rank and falsify competing root-cause hypotheses
  • validate a scoped fix against tests and performance
  • turn a diagnosed bug into regression coverage

Example prompts for the agent

  • Analyze this failure from the reproduction steps, logs, and stack trace, then rank 3–5 hypotheses with evidence for each.
  • Compare the Sentry errors with traces and recent deployment changes without inventing production evidence.
  • Validate the proposed fix by running the test suite, comparing the baseline with the fix, and outlining rollback steps.

How to install error-diagnostics-smart-debug

1Skills CLI (Vercel)

npx skills add sickn33/agentic-awesome-skills --skill error-diagnostics-smart-debug -a claude-code

2Manually: put the files in place

~/.claude/skills/error-diagnostics-smart-debug/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/error-diagnostics-smart-debug/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about error-diagnostics-smart-debug

How do I install error-diagnostics-smart-debug in Claude Code?

Run npx skills add sickn33/agentic-awesome-skills --skill error-diagnostics-smart-debug -a claude-code, then open ~/.claude/skills/error-diagnostics-smart-debug/SKILL.md.

What does error-diagnostics-smart-debug do?

It investigates reproducible and intermittent failures using reproduction steps, logs, traces, and code. The workflow ranks hypotheses, selects a debugging strategy, and validates a scoped fix.

What information should I provide for a diagnosis?

Provide the error or stack trace, reproduction steps, affected components, environment, and failure pattern. Staging or production cases can also use observability data and deployment history.

Source text

SKILL.md · MIT
---
name: error-diagnostics-smart-debug
description: "Diagnose failures from reproduction steps, traces, logs and code; test hypotheses and verify a scoped fix without inventing production evidence."
risk: critical
source: community
date_added: "2026-02-27"
---

## Use this skill when

- A reproducible failure or intermittent incident needs evidence-driven debugging.
- Existing telemetry must be compared with source and deployment changes before patching.

## Do not use this skill when

- The task is unrelated to error diagnostics smart debug
- You need a different domain or tool outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.

You are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis.

## Context

Process issue from: $ARGUMENTS

Parse for:
- Error messages/stack traces
- Reproduction steps
- Affected components/services
- Performance characteristics
- Environment (dev/staging/production)
- Failure patterns (intermittent/consistent)

## Workflow

### 1. Initial Triage
Analyze directly; use a debugger subagent only when the user authorizes delegation and the host exposes that capability:
- Error pattern recognition
- Stack trace analysis with probable causes
- Component dependency analysis
- Severity assessment
- Generate 3-5 ranked hypotheses
- Recommend debugging strategy

### 2. Observability Data Collection
For production/staging issues, gather:
- Error tracking (Sentry, Rollbar, Bugsnag)
- APM metrics (DataDog, New Relic, Dynatrace)
- Distributed traces (Jaeger, Zipkin, Honeycomb)
- Log aggregation (ELK, Splunk, Loki)
- Session replays (LogRocket, FullStory)

Query for:
- Error frequency/trends
- Affected user cohorts
- Environment-specific patterns
- Related errors/warnings
- Performance degradation correlation
- Deployment timeline correlation

### 3. Hypothesis Generation
For each hypothesis include:
- Qualitative confidence and what evidence would change it; do not invent calibrated probabilities
- Supporting evidence from logs/traces/code
- Falsification criteria
- Testing approach
- Expected symptoms if true

Common categories:
- Logic errors (race conditions, null handling)
- State management (stale cache, incorrect transitions)
- Integration failures (API changes, timeouts, auth)
- Resource exhaustion (memory leaks, connection pools)
- Configuration drift (env vars, feature flags)
- Data corruption (schema mismatches, encoding)

### 4. Strategy Selection
Select based on issue characteristics:

**Interactive Debugging**: Reproducible locally → VS Code/Chrome DevTools, step-through
**Observability-Driven**: Production issues → Sentry/DataDog/Honeycomb, trace analysis
**Time-Travel**: Complex state issues → rr/Redux DevTools, record & replay
**Controlled Fault Reproduction**: Use an isolated test environment and bounded authorized faults; never infer permission for production chaos tests
**Statistical**: Small % of cases → Delta debugging, compare success vs failure

### 5. Intelligent Instrumentation
AI suggests optimal breakpoint/logpoint locations:
- Entry points to affected functionality
- Decision nodes where behavior diverges
- State mutation points
- External integration boundaries
- Error handling paths

Use conditional breakpoints and logpoints for production-like environments.

### 6. Production Techniques Requiring Review

Instrumentation, debug endpoints and traffic shifts are changes with privacy, cost and availability effects. Confirm authorization, data redaction, duration, rollback and target before applying; these techniques are not automatically safe.
**Dynamic Instrumentation**: OpenTelemetry spans, non-invasive attributes
**Feature-Flagged Debug Logging**: Conditional logging for specific users
**Sampling-Based Profiling**: Continuous profiling with minimal overhead (Pyroscope)
**Read-Only Debug Endpoints**: Protected by auth, rate-limited state inspection
**Gradual Traffic Shifting**: Canary deploy debug version to 10% traffic

### 7. Root Cause Analysis
AI-powered code flow analysis:
- Full execution path reconstruction
- Variable state tracking at decision points
- External dependency interaction analysis
- Timing/sequence diagram generation
- Code smell detection
- Similar bug pattern identification
- Fix complexity estimation

### 8. Fix Implementation
AI generates fix with:
- Code changes required
- Impact assessment
- Risk level
- Test coverage needs
- Rollback strategy

### 9. Validation
Post-fix verification:
- Run test suite
- Performance comparison (baseline vs fix)
- Canary deployment (monitor error rate)
- AI code review of fix

Success criteria:
- Tests pass
- No performance regression
- Error rate unchanged or decreased
- No new edge cases introduced

### 10. Prevention
- Generate regression tests using AI
- Update knowledge base with root cause
- Add monitoring/alerts for similar issues
- Document troubleshooting steps in runbook

## Example: Illustrative Debug Session

The helpers, spans and metrics below are pseudocode for a hypothetical case; no implementation, telemetry integration or measured improvement is bundled. Replace them with actual configured tools, and never report the example numbers as observed evidence.

```typescript
// Issue: "Checkout timeout errors (intermittent)"

// 1. Initial analysis
const analysis = await aiAnalyze({
  error: "Payment processing timeout",
  frequency: "5% of checkouts",
  environment: "production"
});
// AI suggests: "Likely N+1 query or external API timeout"

// 2. Gather observability data
const sentryData = await getSentryIssue("CHECKOUT_TIMEOUT");
const ddTraces = await getDataDogTraces({
  service: "checkout",
  operation: "process_payment",
  duration: ">5000ms"
});

// 3. Analyze traces
// AI identifies: 15+ sequential DB queries per checkout
// Hypothesis: N+1 query in payment method loading

// 4. Add instrumentation
span.setAttribute('debug.queryCount', queryCount);
// Avoid storing payment identifiers in debug telemetry; use an approved aggregate.

// 5. Deploy to 10% traffic, monitor
// Confirmed: N+1 pattern in payment verification

// 6. AI generates fix
// Replace sequential queries with batch query

// 7. Validate
// - Tests pass
// - Latency reduced 70%
// - Query count: 15 → 1
```

## Output Format

Provide structured report:
1. **Issue Summary**: Error, frequency, impact
2. **Root Cause**: Detailed diagnosis with evidence
3. **Fix Proposal**: Code changes, risk, impact
4. **Validation Plan**: Steps to verify fix
5. **Prevention**: Tests, monitoring, documentation

Focus on actionable insights. Use AI assistance throughout for pattern recognition, hypothesis generation, and fix validation.

---

Issue to debug: $ARGUMENTS

## Limitations
- No supporting scripts or references are bundled in this entrypoint. Tool availability and real trace results must be checked in the current environment.
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

© sickn33 · MIT · sickn33/agentic-awesome-skills

Similar skills

All skills for Backend and APIs →

From the same set187

The whole set →
stitch-ui-design stitch-ui-design guides you in writing prompts for Google Stitch to generate web and mobile UI designs. Use it to specify screens, visual direction, responsive behavior, and interactions. CX Codex +1 2installs programmatic-seo A skill for designing programmatic SEO systems: evaluates feasibility, picks a template strategy, and guards against thin content. CX Codex +1 2installs backend-development-feature-development The backend-development-feature-development skill coordinates feature work from requirements and architecture through implementation, testing, and rollout. Use it for changes spanning services or teams. CX Codex +1 2installs machine-learning-ops-ml-pipeline machine-learning-ops-ml-pipeline — a skill for designing and deploying an end-to-end ML pipeline. Orchestrates specialized agents through data analysis, model training, code optimization, and production deployment with monitoring. CX Codex +1 2installs conductor-manage conductor-manage — a skill that keeps Conductor tracks tidy: finished work gets archived, archived tracks come back, others are renamed or deleted, and leftover artifacts get swept. CX Codex +1 1installs code-refactoring-context-restore code-refactoring-context-restore resumes interrupted development using saved handoff notes and current Git checkout evidence. It checks verified progress against uncommitted edits and plans the next step. CX Codex +1 1installs pricing-strategy pricing-strategy is a Claude Code skill for planning prices, tiers, and monetization around customer value and willingness to pay, including pricing research or an initial pricing model. CX Codex +1 1installs claude-ally-health claude-ally-health organizes user symptom logs and medical records into visit summaries and timelines. Explains clinical terms using external sources and prepares clinician questions. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open