code-observer

Analyze structured logs to reveal code execution paths and error origins.

45|4|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/ewanyuan/cox-coding --skill code-observer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-observer
Source: https://github.com/ewanyuan/cox-coding/tree/main/cn/code-observer
Command: npx skills add https://github.com/ewanyuan/cox-coding --skill code-observer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Code path tracing and debugging: It automatically reveals how code executes, showing which functions run and where slowdowns or errors occur, so you can understand runtime behavior without stepping through with a debugger.

Core Features & Use Cases

  • Execution path discovery: reconstruct the function call graph and timing from logs and metrics.
  • Slow-path analysis: identify hotspots where time is spent.
  • Error localization: locate where exceptions are raised and how they propagate.
  • Cross-dimension analysis: correlate logs with application status, project progress, and test metrics to diagnose issues.

Quick Start

To start a full trace: provide the path to your observability logs and run the tracing pipeline, e.g., "python3 scripts/parse_logs.py --log-file /path/to/log.json --output ./parsed_logs.json" then "python3 scripts/generate_trace_report.py --logs ./parsed_logs.json --output ./trace_report.md"

Frequently Asked Questions about code-observer

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

FAQPage Schema
How do I trace code execution paths from logs to find bugs?

Tracing code execution from logs involves analyzing structured log data to reconstruct function call graphs and identify timing or error origins. This Skill parses observability logs to map runtime behavior and outputs a Markdown report detailing execution paths.

What is the best way to analyze slow performance paths in application code?

Analyzing slow performance paths requires correlating logs with Prometheus metrics and application status to pinpoint timing hotspots. This process identifies where time is spent during execution and isolates the specific functions causing performance degradation.

How do I locate error origins and trace exception propagation without a debugger?

Locating error origins without a debugger is possible by analyzing structured logs and test metrics to identify where exceptions are raised. This Skill traces how errors propagate through the function call graph to reveal exact failure points.

Do I need external dependencies to correlate application status with observability logs?

No external dependencies are required to correlate application status with observability logs beyond Python 3. The Skill relies entirely on bundled scripts to process logs, project data, and metrics for diagnosing reliability issues.

How do I generate a trace report from structured observability logs?

To generate a trace report, parse structured logs using the bundled script to create an intermediate JSON file, then run the report generator script. This outputs a Markdown trace report containing actionable insights for debugging.