Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From mimirs
Assesses blast radius of code changes and reviews diffs by analyzing what touches what, what could break, which tests to run, and prior decisions. Use before refactors, renames, signature changes, or pull requests.
npx claudepluginhub thewinci/mimirs --plugin mimirsHow this skill is triggered — by the user, by Claude, or both
Slash command
/mimirs:reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Goal: know the full impact before and after changing code — no surprise breakage.
Reviews only code changes since last commit using graph-based impact analysis and blast radius detection. Provides token-efficient context for focused reviews of bugs, style, tests, and affected files/functions.
Reviews code changes before merge using Repowise risk scoring and per-file directive analysis to identify breakage risks, missing co-changes, and test gaps.
Reviews git changes with evidence-backed findings and risk-aware verdicts. Supports commit, range, file-scoped analysis, impact assessment, breaking-change detection.
Share bugs, ideas, or general feedback.
Goal: know the full impact before and after changing code — no surprise breakage.
git_context(include_diff: true) for the modified files and the diff.impact <symbol> (transitive callers as a pruned tree + the tests to run). Widen with usages <symbol> (every call site) and dependents <file> (file-level importers). Pass file to impact to disambiguate a name defined in several places.affected for the changed set (CLI: git diff --name-only | mimirs affected --stdin). Run those before claiming the change is done.get_annotations on the touched files: fragile code, constraints, "don't refactor until X".search_checkpoints "<area>" (prior decisions) and search_commits "<area>" (why it changed before), so you don't undo a deliberate choice.impact / affected; annotate any new caveat you introduce; create_checkpoint the decision and what changed.Finish: a risk summary — callers affected, tests to run, caveats, prior decisions — each with a file:line citation.