chat-history

Extract user inputs from Claude Code session history by reading .jsonl session files, filtering out system prompts and tool results, and grouping messages by date. This generates per-day Markdown summaries under a .chats directory for organized documentation.

Export Claude Code .jsonl sessions into Markdown documentation by running an extraction script that parses session logs, isolates user messages, and writes structured daily .md files. This creates a maintainable, changelog-style record for version control.

Organize Claude Code chats into a daily log by grouping filtered user inputs into per-day Markdown files within a project .chats directory. This preserves an auditable history of user instructions and conversation context.

Yes, chat-history requires jq to parse the .jsonl session files. The extraction script relies on jq to filter non-user content and process the raw Claude Code session data into structured Markdown summaries.

Commit Claude Code conversation logs to version control by exporting sessions into a .chats directory containing daily Markdown files. This provides a consistent, auditable changelog-style record of user inputs that integrates with standard version control workflows.

System prompts and tool results are excluded from the daily Markdown summaries to isolate user inputs. Filtering non-user content from .jsonl session files ensures the generated .chats logs focus strictly on user instructions for readable documentation.