Review
Assess the blast radius of a change and review a diff — what it touches, what could break, which tests to run, and the prior decisions behind it. Use before a refactor, rename, or signature change, and when reviewing a pull request or your own uncommitted diff.From its SKILL.md
npx -y skills add TheWinci/mimirs --skill reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.5 KB, as published. Nobody here has run it
Review
Goal: know the full impact before and after changing code — no surprise breakage.
- What changed —
git_context(include_diff: true)for the modified files and the diff. - Blast radius — for each changed function or type:
impact <symbol>(transitive callers as a pruned tree + the tests to run). Widen withusages <symbol>(every call site) anddependents <file>(file-level importers). Passfiletoimpactto disambiguate a name defined in several places. - Tests to run —
affectedfor the changed set (CLI:git diff --name-only | mimirs affected --stdin). Run those before claiming the change is done. - Known caveats —
get_annotationson the touched files: fragile code, constraints, "don't refactor until X". - Why it's like this —
search_checkpoints "<area>"(prior decisions) andsearch_commits "<area>"(why it changed before), so you don't undo a deliberate choice. - After the change — re-run
impact/affected;annotateany new caveat you introduce;create_checkpointthe decision and what changed.
Finish: a risk summary — callers affected, tests to run, caveats, prior decisions — each with a file:line citation.