log-trace-correlation

Map stack trace frames to repository source locations and propose fixes.

1|Updated Apr 19, 2026

Search Tags:#debugging #logs #trace #error-analysis #stack-trace #source-code #path-normalization

Ready to run

npx skills add https://github.com/StepowskiEric/Jerrys-agent-skills --skill log-trace-correlation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: log-trace-correlation
Source: https://github.com/StepowskiEric/Jerrys-agent-skills/tree/main/debugging/log-trace-correlation
Command: npx skills add https://github.com/StepowskiEric/Jerrys-agent-skills --skill log-trace-correlation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Correlate error logs and stack traces to their source code locations to identify root causes quickly and reduce debugging time.

Core Features & Use Cases

Map each frame in a stack trace to the exact file and line number in the repository.
Normalize paths and reveal repo-relative locations across different environments.
Propose a concise, actionable fix hypothesis and outline minimal changes.
Provide surrounding source context to aid rapid diagnosis and validation.

Quick Start

Provide a complete error log with a stack trace, and I will map each frame to the corresponding source code and surrounding context.

Frequently Asked Questions about log-trace-correlation

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

FAQPage Schema

How do I map a stack trace from an error log to the exact source code file and line number?▼

Mapping a stack trace to source code involves parsing error log frames and normalizing paths to repo-relative locations. This process identifies the exact file and line number to pinpoint the root cause quickly.

What is the best way to debug multi-frame stack traces across mixed environments?▼

The best way to debug multi-frame stack traces across mixed environments is through path normalization to reconcile different directory structures. This maps each frame to the corresponding repository file and provides surrounding source context for rapid diagnosis.

Can I get a suggested fix hypothesis when analyzing an error log?▼

Yes, analyzing an error log can generate a concise, actionable fix hypothesis. By mapping the stack trace to source code locations, the process outlines the minimal changes needed to resolve the identified root cause.

Does this approach work for normalizing paths in diverse codebases?▼

Yes, path normalization works across diverse codebases by converting environment-specific directories into repo-relative paths. This ensures accurate file location mapping during stack trace analysis regardless of the original execution environment.

What do I need to provide to start correlating error logs with source code?▼

To start correlating error logs with source code, you need to provide a complete error log containing a stack trace. The tool then parses the trace, normalizes paths, and locates the files to generate an actionable hypothesis.