Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
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.
npx claudepluginhub thewinci/mimirs --plugin mimirsHow 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.
Queries and records architectural decisions (the 'why' behind code) using Repowise. Activates on decision markers like WHY:, DECISION:, ADR: and when 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.
Reads historical intent from Entire checkpoints instead of guessing. Orchestrates sub-skills for code provenance, prior work search, explain, review, session handoff, and dispatch.
Share bugs, ideas, or general feedback.
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.