From traceary
Use when the user asks about prior Traceary sessions, event history, command audits, or what happened earlier in the workspace. Trigger on phrases like "Traceary", "session history", "audit trail", "recent events", or "what happened earlier".
npx claudepluginhub duck8823/traceary --plugin tracearyThis skill uses the workspace's default tool permissions.
Use the packaged `traceary` MCP server as the default read path when the user asks about local agent history.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Use the packaged traceary MCP server as the default read path when the user asks about local agent history.
latest_session: most recent session metadata for the current workspaceactive_session: only when the user is asking about the still-open sessionlist_events: recent history without a keyword filtersearch: keyword-driven lookupsget_context: summarize the lead-up around an eventadd_log or add_audit unless the user explicitly wants to record a new event.