domains / families / devops / error-detective

error-detective

combined

Search logs and codebases for error patterns, stack traces, and Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.

When to use

• Working on error detective tasks or workflows
• Needing guidance, best practices, or checklists for error detective
• Correlating a supplied stack trace with logs and recent code or deployment changes.
• Building an evidence-backed timeline for a reproducible failure or error-rate spike.
• Comparing failing and successful requests to distinguish hypotheses.

When not to use

• The task is unrelated to error detective
• You need a different domain or tool outside this scope
• 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.

Skill page

Conflict

Both copies share the same core procedure (symptom-to-cause, time-window patterns, deployment correlation, cascading failures, error-rate spikes) and the same output list. However, the sickn33 copy adds material constraints and steps the rmyndharis copy lacks: an Evidence and Privacy section (confirm environment/timezone/access, use request/trace IDs, redact sensitive data, do not fabricate sources, mark missing telemetry, read-only boundary), a Limitations section, and a concrete example. The rmyndharis copy is a shorter, less constrained version of the same skill. Crowning one would hide the real alternative of the stricter, privacy-aware procedure.