Search and retrieve bash command history using Atuin. Use when users ask about commands they've run before, want to find a specific command, recall how they did something previously, or ask "how did I..." or "what command did I use to..."
From atuinnpx claudepluginhub nathanvale/side-quest-marketplace-old --plugin atuinThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Orchestrates subagents to execute phased plans: deploys for implementation, verification, anti-pattern checks, code quality review, and commits only after passing checks.
Access bash command history through Atuin to search for and retrieve previously executed commands.
Search for commands matching a query.
Parameters:
query (string): Search term to find matching commandslimit (number, default: 10): Maximum results to returninclude_failed (boolean, default: false): Include failed commandsGet the most recent commands.
Parameters:
limit (number, default: 10): Number of recent commandsinclude_failed (boolean, default: false): Include failed commandsWhen user asks: "How did I deploy last time?"
Use mcp__bash-history__search_history with query "deploy"
When user asks: "What commands did I run recently?"
Use mcp__bash-history__get_recent_history with limit 20
When user asks: "Show me failed git commands"
Use mcp__bash-history__search_history with query "git" and include_failed true
Results include command text, exit code (0 = success), and timestamp. Present clearly and offer to help reuse commands.