// For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
| name | session-search |
| description | For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns. |
If you are Claude Code: Do NOT use this skill directly. Use the
session-searchersubagent via the Task tool instead - it handles this more efficiently without polluting your context.
Search and find previous code agent sessions (Claude-Code or Codex-CLI) for specific work, decisions, or code patterns.
aichat search --json -n 10 "[query]" (use
-g "project" to filter by project)jq to extract fields from JSONL output (session_id,
project, created, snippet, file_path)~/.claude/projects/*/[session-id].jsonl (max 3 files)Run aichat search --help to see all options (date filters, branch filters, etc.)
and JSONL field names.
Return a concise summary containing:
Format as clean markdown, not raw JSON.
Query: "Find sessions where we discussed authentication design"
aichat search --json -n 10 "authentication design"
Summary:
--json flag with aichat search (otherwise it spawns interactive UI)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:
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
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than a direct answer.
This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
Extract full context of the last task from the most recent parent session shown in the session lineage. Strategically uses sub-agents to avoid bloating your own context.
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
Log the work segment that you did after the last work log until now in a