From qrec
Recalls past Claude Code sessions using qrec CLI via Bash. Useful for queries about prior conversations, implementations, decisions, 'last time we...', or previous work.
npx claudepluginhub dvquy13/qrec --plugin qrecThis skill is limited to using the following tools:
Use the qrec CLI to search past Claude Code sessions and answer questions about prior work.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Share bugs, ideas, or general feedback.
Use the qrec CLI to search past Claude Code sessions and answer questions about prior work.
Does the prompt contain any recency signal? Words like "latest", "recent", "pick up", "continue from", "what were we working on", "last time", "last session" — even mixed with topic words like "the latest session on remotion demo" — always mean browse first. Recency signals override topic keywords; don't let topic words push you into semantic search.
qrec search --k 10 (no query → browse mode, date-sorted latest first). You may add --project <name> if the project is unambiguous, but never add a query string.project, title, date fields. Pick the session that best matches the current context — topic words in the prompt help you recognize the right session, not find it via search.qrec get <session_id> and summarize what was in progress.No recency signal — pure topic search — user asks about a specific past decision, implementation, bug, or feature with no "latest/continue" framing:
qrec search "<query>" --k 10 with concrete nouns (function names, error messages, feature names). Narrow with --project <name>, --tag <tag>, --from/--to YYYY-MM-DD if helpful.qrec get <session_id> on the top 1–2 matches and synthesize.Uncertain intent: browse first (qrec search --k 10), fall back to semantic only if nothing relevant surfaces.
# Browse mode — no query, date-sorted (latest first)
qrec search --k 10 # 10 most recent sessions (all projects)
qrec search --project <name> --k 10 # filter to a known project name
qrec search --project <name> --tag <tag> --k 10
# Semantic search
qrec search "<query>" --k 10
qrec search "<query>" --project <name> --k 10
qrec get <session_id> # full session markdown (8-char hex ID from results)
ECONNREFUSED → tell user: qrec serve --daemon