Skill

session-search

Searches prior Claude-Code/Codex-CLI sessions for code patterns, decisions, or work via aichat CLI, jq parsing, and session file reads (max 3). For non-subagent CLI agents.

Bash

Rust

Node

developer-tools

automation

npx claudepluginhub pchalasani/claude-code-tools --plugin aichat

Tool Access

This skill uses the workspace's default tool permissions.

Preview

> **If you are Claude Code:** Do NOT use this skill directly. Use the

SKILL.md

Similar Skills

spec-sessions

Searches coding agent session history to answer questions about past work, previous attempts, investigations, recent activity, or prior sessions—even if not explicitly named.

spec-first

cass

Searches AI coding session histories across Claude Code, Cursor, Aider, ChatGPT, Codex, and Gemini CLI to retrieve prior discussions before new work.

johnlindquist-claude

read-memories

412

Searches past Claude Code session logs to recall decisions, patterns, or unresolved work. Useful when users reference prior conversations, say 'do you remember', or need historical context.

1 tool

duckdb-skills

Stats

Parent Repo Stars1660

Parent Repo Forks103

Last CommitDec 18, 2025

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

If you are Claude Code: Do NOT use this skill directly. Use the session-searcher subagent via the Task tool instead - it handles this more efficiently without polluting your context.

session-search

Search and find previous code agent sessions (Claude-Code or Codex-CLI) for specific work, decisions, or code patterns.

Workflow

Understand the query: Identify what the user is looking for (code patterns, decisions, specific work, design direction)
Search with aichat: Run aichat search --json -n 10 "[query]" (use -g "project" to filter by project)
Parse results: Use jq to extract fields from JSONL output (session_id, project, created, snippet, file_path)
Deep dive if needed: Read session files at ~/.claude/projects/*/[session-id].jsonl (max 3 files)
Summarize: Return a focused summary with key findings and references

Run aichat search --help to see all options (date filters, branch filters, etc.) and JSONL field names.

Output Format

Return a concise summary containing:

Key Findings: 2-3 bullet points answering the query
Relevant Sessions: Session IDs and dates for reference
Specific Content: Code snippets or quotes if directly relevant

Format as clean markdown, not raw JSON.

Example

Query: "Find sessions where we discussed authentication design"

aichat search --json -n 10 "authentication design"

Summary:

Session abc123 (Dec 10): Discussed JWT vs session-based auth, decided on JWT
Session def456 (Dec 8): Implemented refresh token rotation pattern

Constraints

ALWAYS use --json flag with aichat search (otherwise it spawns interactive UI)
NEVER return raw JSON output to the user - summarize and distill findings
NEVER read more than 3 session files per query
If no results found, suggest alternative search terms
ONLY report information directly observed in files - never infer or extrapolate

Error Handling

If aichat search command fails or is not found, ask user to install:

uv tool install claude-code-tools   # Python package
cargo install aichat-search         # Rust search TUI

Prerequisites:

Node.js 16+ (for action menus)
Rust/Cargo (for aichat-search)

If user doesn't have uv or cargo:

curl -LsSf https://astral.sh/uv/install.sh | sh           # uv
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh  # Rust