session-search
session-search queries previous code agent sessions stored locally to find specific work, decisions, or code patterns by running aichat search with JSON output, parsing results with jq, and optionally reading full session files for deeper context. Use this skill when working in CLI agents without subagent support that need to reference past decisions or code implementations across multiple sessions.
git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/session-search && cp -r /tmp/session-search/plugins/aichat/skills/session-search ~/.claude/skills/session-searchSKILL.md
> **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 1. **Understand the query**: Identify what the user is looking for (code patterns, decisions, specific work, design direction) 2. **Search with aichat**: Run `aichat search --json -n 10 "[query]"` (use `-g "project"` to filter by project) 3. **Parse results**: Use `jq` to extract fields from JSONL output (session_id, project, created, snippet, file_path) 4. **Deep dive if needed**: Read session files at `~/.claude/projects/*/[session-id].jsonl` (max 3 files) 5. **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: 1. **Key Findings**: 2-3 bullet points answering the query 2. **Relevant Sessions**: Session IDs and dates for reference 3. **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" ```bash 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: ```bash 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: ```bash curl -LsSf https://astral.sh/uv/install.sh | sh # uv curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh # Rust ```
Extract full context of the last task from the most recent parent session
Use this skill when you learn one or more design pattern(s) in the
Design patterns for the Langroid multi-agent LLM framework. Covers
>-
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.
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.
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