From acdc
Use when the user asks Claude to find content in past sessions by topic or free-text query. Examples include "where did we decide on the ACDC name", "where did I just decide that", "where did we discuss caching last week". For lookup by session name or UUID, use recall-session. For taking over a Codex session, use resume-codex-session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/acdc:recall-contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Ask the user for scope BEFORE running anything:
Ask the user for scope BEFORE running anything:
What scope?
(a) Current session only
(b) Pre-compact (= the earlier part of this session)
(c) Last N days (default 7, customizable)
(d) Since a specific date
Map:
--current--current (helper reads the full JSONL on disk, including pre-compact events)--days N--since YYYY-MM-DDResolve the current transcript path:
$CLAUDE_TRANSCRIPT_PATH~/.claude/sessions/<pid>.json and construct ~/.claude/projects/<escaped-cwd>/<session-uuid>.jsonl (<escaped-cwd> = pwd with / → -)*.jsonl under ~/.claude/projects/<escaped-cwd>/Run the helper.
uv run python <skill-dir>/scripts/grep_recall.py \
--query "<USER_TOPIC>" \
--current-transcript "$TRANSCRIPT_PATH" \
<SCOPE_FLAG>
--cwd-hint $(pwd) to bias toward the current project.--include-tools when the user wants to find content in tool calls (e.g., "where did I use that git command").Present results.
--include-tools.★-marked hit lines and a short paraphrase. Quote the matched preview verbatim.Offer follow-ups:
summarize_claude_transcript.py --from-line=L<seg.lo> --tail=L<seg.hi>grep_recall.pyrecall-session with the resolved UUID--include-tools truncates each tool input to 500 chars.npx claudepluginhub awithi-co/acdc --plugin acdcCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.