Prompt Log

**Quick judgment:** A focused, practical CLI tool for turning Clawdbot/Claude Code/Codex `.jsonl` session logs into readable markdown transcripts. It’s well-suited for developers who already work in the terminal and want to export or slice session histories with minimal setup. **Strengths & scenarios where it works well** - Best when you have one or more `.jsonl` session logs from Clawdbot, Claude Code, or Codex and need a human-readable transcript. - Good fit for auditing past coding sessions, creating documentation of AI-assisted work, or sharing transcripts with collaborators. - Time filters (`--after` / `--before`) make it practical for extracting just the relevant window from long sessions. - Sensible defaults: outputs to `.prompt-log/YYYY-MM-DD-HHMMSS.md` by default, reducing configuration overhead. **Risks, limitations, and caveats** - **Format dependency:** Assumes session logs follow expected structures for Clawdbot/Claude Code/Codex; changes in those formats could break or degrade extraction quality. - **Tooling dependency:** Requires `jq` in `PATH`, and uses `gdate`/`date` on macOS; users without these tools (or unfamiliar with installing them) may hit friction. - **Scope:** It’s narrowly focused on log-to-markdown extraction; it does not provide higher-level analytics, search, or multi-file aggregation out of the box. - **Privacy considerations:** Generated transcripts may contain sensitive code, prompts, or data; users must handle, share, and store these markdown files responsibly. **Recommended usage** Use this skill when you are explicitly asked to: - Export or reconstruct the **prompt history**, **session logs**, or **conversation transcript** from `.jsonl` session files, especially for Clawdbot/Claude Code/Codex. - Produce a markdown transcript from raw session data, optionally constrained to a specific time range or custom output path. It is less appropriate when the user wants interactive log browsing, analytics across many sessions, or support for arbitrary/non-standard log formats.

**Quick judgment**: A focused, low-friction CLI tool that reliably converts Clawdbot/Claude Code/Codex `.jsonl` session logs into readable markdown transcripts, with useful time-based filtering. Well-suited for developers already comfortable with the terminal. **Strengths** - Handles common AI coding session formats directly (Clawdbot, Claude Code, Codex). - Produces markdown output that is easy to store, diff, or share. - Time-window filters (`--after`, `--before`) make it practical for large sessions. - Lightweight dependency footprint (primarily `jq`; optional `gdate` on macOS). **Risks / limitations** - Limited to the supported `.jsonl` log formats; won’t generalize to arbitrary chat logs without adaptation. - Requires shell and CLI familiarity; non-technical users may find it less accessible. - Extracted transcripts may contain sensitive code, credentials, or proprietary discussions; mishandling the markdown files (e.g., committing them to public repos) is a data-leak risk. - Relies on the structure and integrity of the original session logs; corrupted or non-standard logs may yield incomplete or malformed output. **Recommended scenarios** - You need a quick export of your AI coding history (Clawdbot/Claude Code/Codex) for documentation, debugging, or sharing with collaborators. - You want to keep a chronological archive of AI-assisted coding sessions under a project’s `.prompt-log` directory. - You need to isolate a specific time slice of a long session—for example, around the time a bug was introduced—to review exactly what the AI suggested. - You are doing research, compliance review, or incident analysis and need faithful transcripts of what happened in AI coding tools.