domains / families / devops / error-diagnostics-error-analysis

error-diagnostics-error-analysis

combined

You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.

When to use

• Investigating production incidents or recurring errors
• Performing root-cause analysis across services
• Designing observability and error handling improvements

When not to use

• The task is purely feature development
• You cannot access error reports, logs, or traces
• The issue is unrelated to system reliability
• 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

The two copies share the same core procedure (gather context, reproduce, identify root cause, propose fixes) and the same safety constraints. However, the sickn33 copy adds a specific 'Worked example and prerequisites' section that provides concrete diagnostic steps (pinning deployment revisions, comparing pool occupancy, testing N+1 hypotheses) and a 'Limitations' section that the rmyndharis copy lacks. The rmyndharis copy is the cleaner, more general version, but the sickn33 copy contains material steps and constraints that would be lost if the former were chosen as the sole authentic source. Therefore, they should be combined to preserve the specific diagnostic guidance and explicit limitations.