skills.rest
russosalv
russosalvCOMMUNITY
Explore all skills by this author →
GitHub

observability-debug

Correlate traces, logs, and exceptions by ID to identify root causes with file:line precision.

5|Updated Apr 18, 2026
Search Tags:#debugging#logs#observability#triage#traces#root-cause#incident-response
One-click install
npx skills add https://github.com/russosalv/NONoise --skill observability-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability-debug
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/observability-debug
Command: npx skills add https://github.com/russosalv/NONoise --skill observability-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines incident triage by turning dispersed telemetry into a concise timeline, locating the offending code, and proposing actionable fixes with file:line precision so engineers can resolve production errors faster.

Core Features & Use Cases

  • Adapter-driven ingestion: Supports App Insights, Datadog, Grafana+Loki, CloudWatch, OTEL collector, or a generic log file via an adapter contract.
  • Correlation and normalization: Correlates traces, logs, and exceptions by correlation/trace ID and normalizes events into a canonical shape for consistent analysis.
  • Code correlation and remediation: Greps the repository for stack frames, reads surrounding source, reconstructs the call chain, and proposes minimal patches and regression tests.
  • Access-first, read-only workflow: Probes authentication, guides remediation of access failures, and never mutates telemetry backends.
  • Use case: Triage a 500 error reported from production by pasting a correlation ID or scanning recent error clusters to find the root cause and a precise fix.

Quick Start

Ask observability-debug to investigate an incident by pasting a correlation or trace ID or by supplying the path to a local log file.

Frequently Asked Questions about observability-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a production error from traces and logs?▼

Debug observability data by correlating traces, logs, and exceptions by ID, normalizing events into a canonical shape, and mapping them to repository files to identify root causes with file:line precision.

Can I debug incidents using Datadog, CloudWatch, or Grafana and Loki telemetry?▼

Yes, this skill supports adapter-driven ingestion for Datadog, CloudWatch, Grafana and Loki, App Insights, OTEL collectors, and flat log files, normalizing telemetry into a canonical shape for consistent analysis.

How do I triage a 500 error using a correlation ID?▼

Triage a 500 error by supplying a correlation or trace ID, which the skill uses to correlate scattered telemetry, reconstruct the call chain, and return a structured analysis with a proposed patch and regression test.

Does observability-debug propose code fixes for incident response?▼

Yes, this skill proposes code fixes during incident response by grepping the repository for stack frames, reading surrounding source code, and returning a minimal patch with file:line precision alongside a regression test.

Do I need write access to my telemetry backend to investigate logs and traces?▼

No, you do not need write access to investigate logs and traces because the workflow is read-only; it probes authentication, guides remediation of access failures, and never mutates telemetry backends.

What is the best way to analyze flat log files for root-cause analysis?▼

The best way to analyze flat log files for root-cause analysis is using an adapter contract that ingests the logs, normalizes them into a canonical event shape, and maps events to repository files for precise remediation.

Related Skills

Explore More Software Engineering Skills→
narqonarqo
10

Grafana Loki LogCLI

Retrieve time-bounded log entries from Grafana Loki via logcli.

Community
Advanced
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
drvossdrvoss
42

stack-detector

Detect a repository's technology stack and map it to Copilot skills and rules.

Community
Intermediate
VektaVekta
2

diagnose

Diagnose codebase problems by inspecting files, git history, and test cases.

Official
Advanced