log-debugging

Correlate Git worktree context with OTEL JSONL logs to debug Gardener runtime failures.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/carterbs/gardener --skill log-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-debugging
Source: https://github.com/carterbs/gardener/tree/main/.claude/skills/log-debugging
Command: npx skills add https://github.com/carterbs/gardener --skill log-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps debug runtime failures in the Gardener orchestrator by correlating Git context with OpenTelemetry (OTEL) logs, making it easier to pinpoint and resolve issues.

Core Features & Use Cases

  • Log Analysis: Read, filter, and trace OTEL JSONL logs, especially for malformed or high-volume entries.
  • Failure Isolation: Isolate failed runs using run.id or worker identifiers.
  • Context Mapping: Map runtime events and failures back to specific Git worktrees and commit states.
  • Use Case: When a Gardener run fails, use this Skill to trace the exact sequence of events leading to the failure, identify the specific Git commit and worktree involved, and reproduce the issue.

Quick Start

Use the log-debugging skill to trace a failed run with run ID 'your-run-id'.

Frequently Asked Questions about log-debugging

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

FAQPage Schema
How do I debug Gardener runtime failures using OTEL logs?

To debug Gardener runtime failures, this Skill correlates OpenTelemetry JSONL logs with Git worktree, branch, and commit context. It analyzes and filters malformed or high-volume log entries to isolate failed runs and trace the exact sequence of events leading to the failure.

How do I isolate a failed Gardener run by ID in OTEL logs?

You can isolate a failed Gardener run by filtering OpenTelemetry JSONL logs using the specific run ID or worker identifiers. This traces failure events and maps the runtime context back to the corresponding Git commit state for issue reproduction.

Do I need Cargo to trace OpenTelemetry logs for Git context mapping?

You need the OTEL_BIN environment variable or Cargo installed to execute the otel-logs binary. This dependency is required for the Skill to index, trace, and filter OTEL JSONL logs and map them back to Git worktree states.

What is the best way to correlate Git commits with high-volume OTEL JSONL logs?

The best way to correlate Git commits with high-volume OTEL JSONL logs is to filter malformed entries and isolate failed runs by ID. This maps runtime failure events directly to specific Git worktrees and commit states.

Why does tracing Gardener failures fail when OTEL logs are malformed?

Tracing Gardener failures fails with malformed OTEL logs because standard parsers cannot read invalid JSONL entries. This Skill analyzes and filters malformed or high-volume log data to successfully isolate failed runs and trace failure events.