From spec-first
Searches coding agent session history to answer questions about past work, previous attempts, investigations, recent activity, or prior sessions—even if not explicitly named.
npx claudepluginhub sunrain520/spec-firstThis skill uses the workspace's default tool permissions.
Search your session history.
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.
Searches Claude Code conversation history in Scribe DB (SQLite FTS5) or JSONL files to recall past discussions, decisions, code snippets, and context from prior sessions.
Searches prior checkpoints and agent conversations by topic, repo, branch, author, or time window using entire CLI. Summarizes top matches and explains details on request.
Share bugs, ideas, or general feedback.
Search your session history.
/spec:sessions [question or topic]
/spec:sessions
Repo name (pre-resolved): !common=$(git rev-parse --git-common-dir 2>/dev/null); case "$common" in /*) basename "$(dirname "$common")" ;; *) basename "$(git rev-parse --show-toplevel 2>/dev/null)" ;; esac
Git branch (pre-resolved): !git rev-parse --abbrev-ref HEAD 2>/dev/null
If the lines above resolved to plain values (a folder name like my-repo and a branch name like feat/my-branch), they are ready to pass to the agent. If they still contain backtick command strings or are empty, they did not resolve — omit them from the dispatch and let the agent derive them at runtime.
If no argument is provided, ask what the user wants to know about their session history. Use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded) or request_user_input in Codex. Fall back to asking in plain text only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.
Dispatch spec-session-historian with the user's question as the task prompt. Omit the mode parameter so the user's configured permission settings apply. Include in the dispatch prompt: