session-logs

Search and analyze Code Buddy session logs in JSON files.

30|5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/phuetz/code-buddy --skill session-logs-phuetz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-logs
Source: https://github.com/phuetz/code-buddy/tree/main/.codebuddy/skills/bundled/session-logs
Command: npx skills add https://github.com/phuetz/code-buddy --skill session-logs-phuetz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly locate and analyze past conversations and usage metrics within Code Buddy, reducing manual log digging and cost ambiguity.

Core Features & Use Cases

  • Cross-session search and filtering across JSON logs stored under .codebuddy/sessions
  • Distill user and assistant messages, tool usage, and cost data into actionable summaries
  • Audit and trend sessions to identify frequent pain points or cost spikes
  • Use Case: QA teams review weekly chat activity to improve prompts and optimize tool usage.

Quick Start

Use the skill to search for a session by date: rg -l ".codebuddy/sessions/*" | sort | tail -n +1

Frequently Asked Questions about session-logs

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

FAQPage Schema
How do I search Code Buddy session logs for past conversations?

You can search Code Buddy session logs by running the skill to filter JSON files stored under the .codebuddy/sessions directory, using CLI tools like rg to locate specific past interactions.

Can I track API costs and usage metrics from conversation history?

Yes, you can track usage metrics and cost implications by parsing JSON session logs with jq to distill cost data, identifying usage patterns and cost spikes across past conversations.

How do I audit Code Buddy sessions across multiple projects?

You audit cross-project sessions by searching and filtering numerous JSON log files stored in .codebuddy/sessions, analyzing both user messages and assistant tool calls to identify trends.

Do I need jq and rg installed to analyze session logs?

Yes, this skill relies on common CLI tools like jq and rg to parse JSON logs and derive insights from Code Buddy session data, requiring them to be installed in your environment.

What is the best way to identify frequent pain points in chat activity?

The best way to identify frequent pain points is to audit and trend session logs, distilling user and assistant messages into actionable summaries to optimize prompt and tool usage.

Why are session logs not showing up when I search the sessions directory?

Session logs may not show up if the JSON files are not stored in the expected .codebuddy/sessions directory, or if the rg and jq CLI tools lack permissions to read the files.