edi-debug

Locate the active Claude session JSONL file and summarize its metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Telepotch/hirano-edi-on-claude-code --skill edi-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edi-debug
Source: https://github.com/Telepotch/hirano-edi-on-claude-code/tree/main/.claude/skills/edi-debug
Command: npx skills add https://github.com/Telepotch/hirano-edi-on-claude-code --skill edi-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you locate and share the current Claude Code session data by identifying the active session JSONL file and presenting a ready-to-share summary, saving time when debugging or collaborating with developers.

Core Features & Use Cases

  • Session discovery: Detects the active Claude session and maps it to a JSONL file on disk.
  • Summary extraction: Produces basic session metadata (ID, size, timestamps) and ready-to-send references.
  • Collaboration: Opens the file location in Finder for quick sharing with teammates or developers.
  • Use Case: You need to review the latest user messages and timestamps to diagnose a defect in the Claude Code workflow.

Quick Start

Run the skill to locate and preview the current session JSONL file.

Frequently Asked Questions about edi-debug

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

FAQPage Schema
How do I find the current Claude Code session JSONL file for debugging?

To find the current Claude session JSONL file, the skill locates the active Claude parent process, maps its PID to the corresponding session file on disk, and verifies the file path exists before presenting a concise summary.

What is the best way to share Claude session logs with developers?

The best way to share Claude session logs is to use a skill that identifies the active JSONL file and opens its location in Finder, allowing you to quickly send the session data to teammates for collaborative debugging.

Can I extract metadata like ID and timestamps from a Claude session log?

Yes, you can extract basic session metadata like the ID, file size, and timestamps from a Claude session log by running the skill, which produces a ready-to-send summary of the current session data.

How does mapping a process ID to a session file work in Claude?

Mapping a process ID to a session file works by locating the active Claude parent process, using its PID to identify the matching JSONL file on disk, and verifying the file path exists before opening it for review.

Why should I use a dedicated session finder instead of manually searching for JSONL logs?

You should use a dedicated session finder because manually searching for JSONL logs is time-consuming, whereas the skill automatically detects the active session, verifies the file path, and extracts ready-to-share metadata for debugging.