skills.rest
RaNDoM6913
RaNDoM6913COMMUNITY
Explore all skills by this author →
GitHub

debug-observer

Collect and correlate logs, database state, cache state, and Git changes across services.

1|Updated Mar 23, 2026
Search Tags:#git#debugging#logs#redis#docker#diagnostics#traces
One-click install
npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill debug-observer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-observer
Source: https://github.com/RaNDoM6913/claude-code-superkit/tree/main/packages/codex/skills/debug-observer
Command: npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill debug-observer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug issues by collecting and correlating logs, database state, cache state, recent git changes, and request execution traces across a project.

Core Features & Use Cases

  • Multi-source data collection across containers, databases, caches, and code changes for rapid triage.
  • Automated trace assembly linking events to requests, endpoints, and entities.
  • Use Case: When an incident occurs, quickly surface the root cause by cross-referencing logs with DB or Redis state and recent commits.

Quick Start

Provide an Entity ID or Endpoint to trigger an end-to-end diagnostic trace.

Frequently Asked Questions about debug-observer

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

FAQPage Schema
How do I debug a distributed stack by correlating Docker logs with database and Redis state?▼

To debug a distributed stack, this Skill collects and correlates Docker logs, database state, cache state, and recent Git changes across services. It automatically detects infrastructure via docker-compose and environment context to surface an execution trace for rapid triage.

What is the best way to triage incidents in a Dockerized environment?▼

Triage incidents in a Dockerized environment by cross-referencing application logs with DB or Redis state and recent commits. Automated infrastructure detection via docker-compose links events to requests and entities to quickly surface root causes.

Do I need to provide an Entity ID or Endpoint to start debugging?▼

Yes, providing an Entity ID or Endpoint triggers an end-to-end diagnostic trace. This input links events to requests and entities across your services to initiate the cross-referenced investigation.

Can I use this to investigate performance issues across docker-compose service stacks?▼

Yes, this supports performance investigations across docker-compose service stacks. It applies automatic infra detection to collect multi-source data and assemble an execution trace linking events to endpoints.

How does automated infrastructure detection work for collecting diagnostics?▼

Automated infrastructure detection works by reading docker-compose, service stacks, and environment context. This identifies running services to collect and correlate logs, database state, and cache state into a unified trace.

Related Skills

Explore More Software Engineering Skills→
PaparusiPaparusi

docker-manager

Manage Docker containers, images, and compose stacks via CLI commands.

Community
Intermediate
jdeweedatajdeweedata

Bug Fixing Assistant

Diagnose and fix bugs in the CircleTel codebase using a five-phase debugging workflow.

Community
Advanced
michaelayoademichaelayoade

debug-stack

Correlate Docker container logs, database records, and Redis state to diagnose production failures.

Community
Advanced
api7api7
1

a6-plugin-skywalking

Configure APISIX SkyWalking tracing integration for distributed traces.

Official
Advanced