From mimirs
Retrieves the rationale and history behind project decisions using commit logs, checkpoints, and conversation archives. Use to avoid undoing deliberate choices or to understand why something was done.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mimirs:recallThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Goal: find the reasoning and history behind code, not just the code.
Goal: find the reasoning and history behind code, not just the code.
search_commits "<topic/decision>" for the commits that explain a change and the intent behind it; file_history <file> for how a specific file evolved.search_checkpoints "<topic>" for recorded decisions, milestones, and direction changes.search_conversation "<topic>" for the back-and-forth that led to a choice, including alternatives considered.Finish: state the decision/history with its source (commit hash, checkpoint, or session) so the answer is traceable. If the history shows a deliberate choice, surface it — don't silently undo it.
npx claudepluginhub thewinci/mimirs --plugin mimirsQueries project memory to recall context, decisions, and history. Use before starting work, investigating unfamiliar code, or asking about past decisions.
Explains why code is built a certain way by surfacing architectural decisions from git history, comment markers, and Repowise-indexed ADRs. Helps maintain alignment before making architectural changes.
Answers hard open-ended questions about how a project works by synthesizing code, structure, git history, decisions, and discussion across multiple areas.