Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/fabriq:history <channel-id>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# fabriq history Run `fabriq history $ARGUMENTS` and present the output to the user. The CLI prints messages oldest-first, one per line, with timestamp, short sender id, and body. Just show that output verbatim — don't reformat or summarize unless the user asks. If there are no messages, say "no messages yet" and stop.
Run fabriq history $ARGUMENTS and present the output to the user.
The CLI prints messages oldest-first, one per line, with timestamp, short sender id, and body. Just show that output verbatim — don't reformat or summarize unless the user asks.
If there are no messages, say "no messages yet" and stop.
npx claudepluginhub nagarjun226/fabriq-dist --plugin fabriq/historyQueries past Claude Octopus workflow runs from local run-log.jsonl, showing last N or filtered by workflow type, date, provider; supports stats and experiments.
/historyResearches historical attempts, successes, failures, and lessons for a problem/approach (or current context) via interactive questions, producing a structured report with summaries and patterns.
/historyLists past OCR review sessions from .ocr/sessions/ in reverse chronological order as a table with session ID, target, reviewers, and verdict.
/historySearches Claude Code, Codex, and Hermes conversation history in parallel with optional date, source, and limit filters.
/historyAnalyzes commit history of a GitHub/GitLab repo to discover debugging patterns, workflows, refactoring strategies, and improvements, suggesting applications to the current project.
/historyDisplays recent bash command history (last 20 commands) with success/fail status, timestamps, working directories, session IDs, and offers to analyze or answer questions about it.